Don't look up the method age during deferred compilation. #405
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.
The following MWE:
... resulted in an abort:
The reason being that we look up the method's age using a generated function that gets invalidated when a function is redefined. However, lacking JuliaLang/julia#48611 we don't actually know the world we're generating code for, so we use the current world age. Turns out that can be too new for the world we're emitting code for, triggering an assertion when our generator returns a ci with those bounds set.
As this only happens with deferred codegen, work around this by not looking up the age of the method, as we'll override it during codegen anyway with the parent's age.