-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inference regression on master in code that sorts arguments by type #24860
Comments
(0.6 bug) fixed by #23912 |
Note: this looks like a variation on the common "tuple split" pattern used in base in a couple places (most notably perhaps, right now, being sparse broadcast "capturescalars"). I think there is likely a variant of this that will still be inferable, although it may require creative thinking to sort out. |
OK, thanks. For reference, it looks like simply changing all of the |
Er, sure, yes, simply disabling correctness is one solution. |
Consider the following code (see https://discourse.julialang.org/t/function-with-unordered-parameter-list/7383/6?u=tkoolen for context and explanation):
On 0.6.1, the
code_warntype
shows that the return type is inferred asas I had hoped, but on one-day-old nightly (Julia Version 0.7.0-DEV.2692, Commit 710a3d8* (2017-11-29 07:44 UTC)), the return type is inferred as
Tuple{Vararg{ParticleType,N} where N}
It should also be noted that on 0.6.1, calling
sort_particle_types
from global scope results in aStackOverflowError
in inference code (https://gist.github.com/tkoolen/8c3eb36aba92da194e84725c2eab18f6), whereas the function does return as expected on nightly.The text was updated successfully, but these errors were encountered: