in a word, swap "." and "_" (except that in number literal, and 11l keyword), consider "." valid in identifiers and "_" becomes a binop.
(this idea is general to languages, but works even better on 11l)
that has several pros:
member access and number literal never collides. 1.5_toString() needs no space.
"_" is usually longer than "." under proportional font, that corresponds to member access should look "more delimited".
snake case never needs shift key (although there's intellisense already)
in the 11l case, the tree-like keyword keeps using "." looks (and conceptually) more like a whole token, which is more consistent.
(this idea is general to languages, but works even better on 11l)
that has several pros:
member access and number literal never collides. 1.5_toString() needs no space.
"_" is usually longer than "." under proportional font, that corresponds to member access should look "more delimited".
snake case never needs shift key (although there's intellisense already)
in the 11l case, the tree-like keyword keeps using "." looks (and conceptually) more like a whole token, which is more consistent.