From 3377fb9ba36800fd3f40616e3906d0f22228c740 Mon Sep 17 00:00:00 2001 From: Runxi Yu Date: Thu, 5 Dec 2024 20:51:59 +0800 Subject: New repo locations and file structure --- reasoning | 10 ---------- 1 file changed, 10 deletions(-) delete mode 100644 reasoning (limited to 'reasoning') 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. -- cgit v1.2.3