C++17 suggestions

The standard pointer\reference notation should be depreciated. Language changes: The new way will be fashioned after templates. There is only pointer<T>, and optimization of how it is treated is left to the compiler.

Library additions: A full featured non-axiomatic set theory library. The standard operations of union, intersect, power set, are all implemented of in an unordered container, and can handle comprehensions and infinite lists. Also contains functions for Cantor's method of coding to determine countability, and checking the injectiveness and bijectiveness of mappings between two sets (possibly done at compile time). Also, that cocksucker Russell can keep his fucking types and classes, these sets can eat themselves.

>>25
Ahh, that reminds me of the exact thing that Sepples17 needs. Annotations! Just like Java! No more will we be confused when we override a method function from the super-super-super-super-super-class when errors are thrown without @override. Another thing could be mandatory exception handling. Don't have twenty exception handlers for everything that can go wrong with std::cout? You get that sweet, sweet five-hundred-line compile error barf that only C++ can give.