On Tuesday, 7 June 2016 at 17:04:19 UTC, jmh530 wrote:
How about no headers or macros?
Textual include files are annoying and C++ needs more symbolic modules, but not having the ability to use namespaces is annoying too and D's take on name resolution can break code.
No need to use macros in C++10, but it comes in handy in debugging and unit testing, actually. So, I am bit torn on that.
So those are just break-even issues, neither better or worse. Plusses and minuses in both camps.
Dub?
Not a language feature, I avoid to use such features if I can. I really hate being forced to use it with node.js. I prefer downloading directly from github and put specific versions of libraries in my own projects. I don't use a package manager with Python either. Just download libraries, remove unneeded stuff and dump it into my project directory.
Chaining range operations with ufcs?
I don't like how UFCS makes code less maintainable, and was happy to learn that C++17 most likely won't add it.
I only use generators for testing, not for production. In general I end up using explicit easy to read inner-loops as they are easier for step-debugging and easier to optimize. The time it takes to write the code is less costly than the time it takes to understand what is going on in a debugger.
I use generators in high level REPL languages like Python though.
