-
-
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
type inference problem (regression?) in nightly #36486
Comments
Here's the code_warntype for 1.4.1, for completeness:
|
Looks similar in nature to #35800. |
I don't think we saw these errors going back to May. It's just been in the last couple of weeks, but I'll need to check. |
We were good as of June 4 at the earliest; perhaps even later than that: sbromberger/LightGraphs.jl#1440 |
@abhinavmehndiratta noticed that the inference issues only happen when the vector returned is empty. If the vector contains values, then no inference error is generated in our test code. |
For the last several days, our CI for nightly has been failing with an unexpected type inference issue. This is as minimal a WE as I can come up with right now (and it's not really minimal, so my apologies):
This infers correctly on 1.4.1 but does not on 1.6.0-dev.
The call is actually just this:
and each possibility returns a
Vector{eltype(g)}
. (Edit: that is, if you run the function in each branch by itself, it infers correctly.)Again, this is fine in 1.4.1 but breaks in 1.6.0.
The text was updated successfully, but these errors were encountered: