3 ms·
So basically, error handling code? I apologize, but I don't see what's new in this?
by quickben 10y ago
So basically, error handling code? I apologize, but I don't see what's new in this?
- lgas 10y agoAll of your error handling code re-writes functions in live code to replace failing function calls with calls to function that would succeed?
- astrobe_ 10y agoNo, because that would be stupidly expensive. Besides, it would introduce a second problem: fixing the healing code - more specifically the parts that validate the candidate functions, which can be bugged as well as anyone who as written automated tests knows. But I guess that saying that your system died from autoimmune disease is way more "exciting" than saying that it died from a segfault.
- juskrey 10y ago"system died from autoimmune disease" - this is gold! I can't imagine why would anyone want to have an untested set of semibuggy functions just to replace them at will. However, I can imagine the tinkering code approach, not "self-healing", when we are expecting ALL functions to be good, it is just we don't know which one fits better to the situation. People actually do this all the time since the beginning of the history, but perhaps the discussed approach can introduce more abstract framework for that.