3 ms·
I get the feeling that your knowledge of the rules is not necessarily representative of typical post-1.0 developers. :-) However, I don't recall it being a pro
by marshray 13y ago
I get the feeling that your knowledge of the rules is not necessarily representative of typical post-1.0 developers. :-)
However, I don't recall it being a problem in my experimentation with Rust either.
- TylerE 13y agoIn my case, it's not a problem with understanding them, it's a burning desire that they not exist.
- klibertp 13y agoYou realize that it's a matter of aesthetics at best? You could set your editor of choice to substitute character ; with <pink elephant> when displaying code and back when saving it to disk. Have you tried this approach? (It's not an original idea - there is a plugin for Emacs which does exactly this for CamelCase - it displays parts of camel cased words as separate words. Helpful if you have looong camel cased name and are irritated because <back by word> and <forward by word> doesn't take you where you should be)
- TylerE 13y agoNot just aesthetics, it's also a matter of ergonomics. ; is not the most comfortable thing to type, requiring either wrist rotation or an awkwardly bent pinky.
- shrughes 13y agoDvorak does it better -- underscore is on the home row.
- marshray 13y agoThat's odd, I consider ';' as one of the easiest things to type. What kind of keyboard are you on? I'm a C++ developer and go so far as to make it harder. I map ; to <esc> in vim, and enter the actual char with a second ; (from from normal mode).