aboutsummaryrefslogtreecommitdiff
path: root/reasoning
diff options
context:
space:
mode:
Diffstat (limited to 'reasoning')
-rw-r--r--reasoning2
1 files changed, 1 insertions, 1 deletions
diff --git a/reasoning b/reasoning
index a0d3f2a..090090d 100644
--- a/reasoning
+++ b/reasoning
@@ -3,7 +3,7 @@ Some reasons for some stuff done here. Not going to be a part of the specificati
nofail:
If you can get into a situation where there's no way to free resources you no longer need, you have done something wrong.
If the language doesn't give you a way to do the above, the language has done something wrong.
- free(), close(), and other such should be marked as `nofail`, so that you don't run out of stack space trying to call them, resulting in inability to free resources.
+ free(), close(), unlocking, and other such should be marked as `nofail`, so that you don't run out of stack space trying to call them, resulting in inability to free resources.
Good for situations where failing to call a function partway through is deemed (by the programmer) undesirable.