Separate resolveType and checking for recursion #408
Merged
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 commit refactors
resolveType
so that the checking for recursivetype synonyms is not done for every lookup. This allows it to be lifted
out of the state monad (which is the main reason for this refactoring).
Instead there is a function
resolveTypeAndCheckForLoops
that does whatresolveType
did before, and this function is called when prechecking atype synonym. This is done with minimal code duplication by also
refactoring resolving of ref types into its own function.
Also fixes issue #413.