You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Identifiers should have clear names and don't use abbreviations as this makes them a lot more clear and easy to read. For example, having a function called lessThan is easier to understand than lt. The same applies for length over len
As most of the current identifiers are no abbreviations as well it would make the library much more consistent with the rest of the language.
The text was updated successfully, but these errors were encountered:
There is a broader point here: should we develop a design guide for the standard library proposals? The Web has https://w3ctag.github.io/design-principles/. TC39 has thought about making a "rationale" repo; maybe this should go there.
littledan
changed the title
Prefer readability
Design guidelines for new library features
Dec 20, 2018
Identifiers should have clear names and don't use abbreviations as this makes them a lot more clear and easy to read. For example, having a function called
lessThan
is easier to understand thanlt
. The same applies forlength
overlen
As most of the current identifiers are no abbreviations as well it would make the library much more consistent with the rest of the language.
The text was updated successfully, but these errors were encountered: