diff options
| author | Runxi Yu <me@runxiyu.org> | 2024-12-05 20:51:59 +0800 |
|---|---|---|
| committer | Runxi Yu <me@runxiyu.org> | 2024-12-05 20:51:59 +0800 |
| commit | 3377fb9ba36800fd3f40616e3906d0f22228c740 (patch) | |
| tree | 0fee14fc1518b61d384ec79c549fc56e3de8f109 /reasoning | |
| parent | e2 in plain text (diff) | |
| download | e2-spec-3377fb9ba36800fd3f40616e3906d0f22228c740.tar.gz e2-spec-3377fb9ba36800fd3f40616e3906d0f22228c740.tar.zst e2-spec-3377fb9ba36800fd3f40616e3906d0f22228c740.zip | |
New repo locations and file structure
Diffstat (limited to 'reasoning')
| -rw-r--r-- | reasoning | 10 |
1 files changed, 0 insertions, 10 deletions
diff --git a/reasoning b/reasoning deleted file mode 100644 index 090090d..0000000 --- a/reasoning +++ /dev/null @@ -1,10 +0,0 @@ -Some reasons for some stuff done here. Not going to be a part of the specification, just ideas for why. - -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(), 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. - - Also usable for times when you don't want to have to deal with failure. |