Use C++11 (or 14) features by default #122
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
C++14 is the default starting in GCC 6.1, released April 2016.
C++14 is the default starting in Clang 6.0, released March 2018.
We had minimal problems* with using C++11 features by default this semester in some of the labs (see: Lab 6
<chrono>and Lab 11<random>).So, I think it's safe (and beneficial) to teach and use C++11/14 features as much as possible rather than relying on older functionality.
This PR updates both the slides and the labs.
Notably:
nullptrto non-pointers)* Some Clang versions on Mac seem to not like nested templates without spaces, but that's very minor and they were able to figure it out by themselves every time.