-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roadmap for C++14 #69
Comments
I wouldn't mind moving to C++14, but I really don't have the time or opportunity to handle this myself (I don't work with C++ anymore). |
I'd like to create a bulk PR moving from Boost compatibility stuff like Boost.Move, Boost.SmartPtr, Boost.Bind to the C++11 versions to reduce dependencies especially as Boost 1.73 throws warnings with current usage of Boost.Bind. To not waste any effort: In what granularity do you want the PR(s)? It is mostly a Search&Replace so I'd put everything that can be done by S&R into 1 PR, likely in different commits per Boost lib. Is that fine? Oh and: C++11 or C++14? See above for mostly |
Yes I think both are fine: C++14 and one PR. Thanks for doing this! |
While doing this I came upon the format/serialize/stream stuff (log.hpp, stream.hpp, format.hpp) There are many functions and they still don't cover everything. An alternative would be to use a single Not sure if it is worth it, just wanted to mention it to not forget |
Are there any plans for C++11/C++14 inside the framework? I believe quite some trickery and macros can be removed which makes the code cleaner to understand and use. Furthermore
override
andnoexcept
shall be supported too (see #49) which is hard to impossible without raising the minimum requirements.We recently switched to C++14 too and most of the boost code used basically vanished and code is now easier to read an test.
Suggestion:
std::trait_t
instead oftypename std::trait::type
])The text was updated successfully, but these errors were encountered: