-
-
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
Unreachable reached #30122
Comments
Looks like the
in particular because of this:
|
Reduced:
gives zero matches, despite:
|
Or even simpler:
is giving the wrong answer. |
Thanks for the amazing work of tracking it down! I wonder whether it's possible to detect issues like that earlier (during type inference or compilation). |
Not really, what you're seeing is already the result of extra code inserted to make these sorts of issues obvious. The compiler thought one thing was gonna happen, but another thing did. |
I'm very sorry for pinging this issue: I know/see you are very busy improving various aspects of Julia. |
I'm looking at it now. Ok to ping issues to gently remind us; thanks for your patience. |
I hit "Unreachable reached" error with Julia 1.0.2 on Archlinux, then I tried backports-1.0.3 branch, assuming that #29986 will fix the problem, but it's still there.
Unfortunately, I don't have a small reproducible test case: it happens when I try to run the
]test BlackBoxOptim
using pareto_rtree branch, which requires SpatialIndexing master (not yet in Julia registry).Here's the log:
Here's the code in question:
It looks like the error happens immediately before/after
_subtract!()
returns tosubtract!()
.I think it's related to the concrete types of the
RTree
andNode
, because this code runs fine inSpatialIndexing
tests (nodetype(tree) = SpatialIndexing.Node{Float64,3,SpatialElem{Float64,3,Int64,String}}
), but fails when (nodetype(tree) = SpatialIndexing.Node{Int64,2,BlackBoxOptim.FrontierIndividual{BlackBoxOptim.IndexedTupleFitness{2,Float64}}}
).Since it looks like it's type-related, I thought that it might be similar to #30067.
The text was updated successfully, but these errors were encountered: