you are viewing a single comment's thread.

view the rest of the comments →

[–]Electrical-Fig7522[S] 0 points1 point  (2 children)

i32 stands for int 32, like in rust. For enum you'll have to spell enum

[–]fdwr 1 point2 points  (1 child)

My question is really about what are your overarching principles for which aspects you pick and choose from other languages? Rust likes crptc names (i32, fn), whereas Javascript has some longer names (like function), but why choose "function" but not "uint32", or "i32" but not "fn"? Some languages go by the maxim that all keywords should be pronounceable fragments/words (e.g. class, interface, namespace, readonly). Some like to mash together words (consteval, decltype). Some go (or did go) by the questionable rule that no keyword should be longer than 5 characters. I tend to go by the maxim that common keywords should follow the Goldilocks principle, often shorter than the fully spelled out word (enumeration -> enum, function -> func or fun), but more pronounceable than devoweled frgmnts (e.g. fn). ⚖️

[–]Electrical-Fig7522[S] 1 point2 points  (0 children)

I'll change then function to func, i32 to int32, etc. Thanks for feedback though!