inference: relax type_more_complex for Type #42901
Merged
Conversation
This file contains hidden or 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
If the object is not a potential Type{...}, we can allow greater
flexibility in recursion.
|
Seems to also fix #42839 |
ianatol
pushed a commit
to ianatol/julia
that referenced
this pull request
Nov 5, 2021
ianatol
pushed a commit
to ianatol/julia
that referenced
this pull request
Nov 5, 2021
66 tasks
|
I've backported this to the backport-release-1.7 branch to run a PkgEval (I am assuming this will be merged here at some point). |
LilithHafner
pushed a commit
to LilithHafner/julia
that referenced
this pull request
Feb 22, 2022
If the object is not a potential Type{...}, we can allow greater
flexibility in recursion.
LilithHafner
pushed a commit
to LilithHafner/julia
that referenced
this pull request
Mar 8, 2022
If the object is not a potential Type{...}, we can allow greater
flexibility in recursion.
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.
If the object is not a potential Type{...}, we can allow greater
flexibility in recursion. And for Vararg too.
Fixes #42835