Better error messages when students use custom types in collections. #71
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.
This edit introduces a bunch of extra
static_assert
checks that give cleaner error messages when students interact with our container types. For example, if you make aVector<T>
for a custom typeT
that isn't hashable, then callinghashCode
on that vector gives a sensible error message about needing to define a hash code for the custom type. The same is true for relational operators, stream insertion, and stream extraction, and these assertions are there for all our containers, not justVector
.This is essentially a fix for #65 but goes much beyond the
Vector
type.