This repository was archived by the owner on Apr 15, 2022. It is now read-only.
Improve type name handling #15
Merged
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 PR makes two changes to make
TypeNamemore useful:type_nameassociated function to theDescribetrait to directly get the type name for any type implementingDescribe. As as result, all primitive types now have an associated type name.type_paramsfield toTypeNameto ensure that different monomorphizations of a generic type can be differentiated by their type name (as described in TypeName doesn't account for generics #12).Together these changes make it easier to use
TypeNameto uniformly reference a type without needing to fully describe a type.Closes #12