-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Tuple bug (getindex
has no method matching getindex(::Void, ::Int64))
#11357
Comments
getindex
has no method matching getindex(::Void, ::Int64))getindex
has no method matching getindex(::Void, ::Int64))
See also #11278
This is kind of tricky because it is dying inside type inference. If you don't mind using gdb, you could run Alternatively, if you can provide a minimal repro script, that would be helpful (requiring to clone/use your package is ok if you can't reduce it) |
I think this is a reduced test case:
In the future, it's good to provide instructions for reproducing the bug even if it involves running a huge program and you don't have a reduced case. |
Thanks, Jeff! I will do so in the future. |
I ran into what appears to be a bug involving the new tuple types using the latest Julia nightly (julia-0.4.0-c777d31727-osx).
There is a type,
ByteRGB
, which I want to change to a tuple type, so I replaced thiswith this:
which results in this when running a program that works fine with the non-tuple definition:
Line 113 in placepixels.min.jl is
candidate = nearest(canvas.frontier, color)
where color is of typeByteRGB
and the functionnearest
is defined inside a package I wrote.The full program is somewhat extensive and I haven't been able to successfully make a reduced test case. If the bug is not diagnosable from the information I've given here, then I can try to get a better stack trace. What's the best way to do so?
The text was updated successfully, but these errors were encountered: