31–34 of 34 posts
That's very nice and I'll probably be using it a lot, after VS2019 will stabilize (it's just a preview now). However, the fact that this thing works so well, says a lot about the design of C++ standard library. They should have encapsulated the pair of iterators into a single structure, and implement implicit casts from vectors/arrays to that object. Requiring to type begin/end every single time is counterproductive.
I despise code autocomplete features. I could not stand using Jedi in Emacs. It just slows me down way too much to have to interact with an autocompleter. I’ll never understand why anyone would want this. I’ve found code autocompletion to be particularly troublesome and hindering on large legacy code bases, where the suggestions not only prevent you from quickly typing out the method, class, etc. that you were trying…
I've never found any of the autocompletion packages emacs had useful, mainly because their implementation continuously broke and they never felt solid. The story is completely different in visual studio code or visual studio for that matter.
I despise code autocomplete features. I could not stand using Jedi in Emacs. It just slows me down way too much to have to interact with an autocompleter. I’ll never understand why anyone would want this. I’ve found code autocompletion to be particularly troublesome and hindering on large legacy code bases, where the suggestions not only prevent you from quickly typing out the method, class, etc. that you were trying…
I've never found any of the autocompletion packages emacs had useful, mainly because their implementation continuously broke and they never felt solid. The story is completely different in visual studio code or visual studio for that matter.
I did not find them useful because autocompletion while writing code is itself just not a useful tool conceptually, regardless of the quality of the tool.
Autocompletion for coding just doesn’t have any mainstream use cases or situations in which it can possibly be helpful. As a result, even very well made autocompletion tools cause trouble and hinder productivity.
On the other hand there can be niche, non-mainstream uses, like accessibility use cases for disabled people who have to use key entry mechanisms that make non-autocompletion key entry overly burdensome or slow.
I despise code autocomplete features. I could not stand using Jedi in Emacs. It just slows me down way too much to have to interact with an autocompleter. I’ll never understand why anyone would want this. I’ve found code autocompletion to be particularly troublesome and hindering on large legacy code bases, where the suggestions not only prevent you from quickly typing out the method, class, etc. that you were trying…
I've never found any of the autocompletion packages emacs had useful, mainly because their implementation continuously broke and they never felt solid. The story is completely different in visual studio code or visual studio for that matter.