larvit/fejkdata
3
0
Fork 0
Code Pull Requests 1 Actions Activity

Define what one meaning is in the naming decision

Browse Source
This commit is contained in:
Lilleman auf Larv
2026-09-25 19:18:23 +02:00
committed by Lillem4n
parent b38974adb2
commit c0cbb71d26
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/decisions.md
+6 -5
View File
@@ -310,11 +310,12 @@ file the stem of the units it holds.
## One name, one meaning ## One name, one meaning
Two declarations of any kind — function, method, field, type — share a name only where Two declarations of any kind — function, method, field, type — share a name only where
they name one thing: an interface's method, `Fake` on each template kind, a field one definition covers both: the same kind of value, counted or addressed the same way, so
holding what a same-named method returns, `renderScope.hold` answering with a `*hold`. a reader landing on the wrong one concludes nothing false. `Fake` on each template kind
A bare function never shares a name with a method, since grep cannot tell a bare call renders one value from what it is called on; `renderScope.hold` returns the `*hold` it
from a method's; `TestNoFunctionSpellsAMethod` holds that, and review judges the rest, names. A bare function never shares a name with a method: a search for the name returns
which is meaning no test can see. Serves goal 2: names that tell the truth, and reaching both, and a call site shows no receiver to tell them apart. `TestNoFunctionSpellsAMethod`
holds that, and review judges the rest. Serves goal 2: names that tell the truth, and reaching
the unit behind a symptom without asking a person. Decided 2026-09-25 by Lilleman; valid the unit behind a symptom without asking a person. Decided 2026-09-25 by Lilleman; valid
while goal 2 counts reading cost. while goal 2 counts reading cost.