Type aliases, take #N #357
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
… differ from the target type
…ructibles in a given scope tree
… generic parameters
…nd we incur into a 'missing constructor' error
…d generic input parameter
|
/ok-to-test sha=d075ec6 |
…her than the trait, when resolving trait methods
LukeMathWalker
force-pushed
the
hate-type-aliases
branch
from
d075ec6 to
1befce5
Compare
|
/ok-to-test sha=1befce5 |
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.
While dog-fooding Pavex, I ran into an issue with type aliases.
It led me to rework part of the reflection engine to properly normalize type, fix the way primitive types are handled (due to a difformity in the JSON output) as well as some diagnostic improvements here and there for easier debugging.
A proper side quest, unfortunately.