-
-
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
show fails with TypeConstructor #5497
Comments
Sure enough, reverting that changes fixes the issue, but why is that method even getting called at all? |
|
The weird thing is that the TypeConstructor exception is being thrown for the display of the +(DiagonalMatrix, Matrix) method, which has nothing to do with MIME types. It's barfing on string(Matrix), I think, but only in this context. My current theory is that we are seeing a random side effect of some other bug in Julia. |
Yeah, that's why I'm hesitating to just revert that change – I think this is exposing some other breakage. |
I found out that the bug is intermittent, things sometimes work when restarting julia. However, reverting that commit makes it disappear for some reason. Also, this can be reproduced as simply as this:
More data: say we have put the
the bug shows up when calling
The called method should just do this:
but when this is called directly, it always works:
Judging from In any case the commit indicated by git blame should be unrelated. Wild guess: maybe something funny is going on with the inlining step while choosing the |
I can't reproduce any of the |
Yeah, I think this issue is a bit stale. |
I see this issue is closed, but I get this error when reloading a module I'm working on.
|
See #8163. |
This afternoon, @StefanKarpinski and @loladiro and I hit a bug. If you type
methods(+)
in the REPL, you get:The problem seems to be that
show(x::DataType)
expectsx.name.name
to exist, butTypeConstructor
(x.name
?) does not have this field. (I'm actually not even sure whatTypeConstructor
is; I can't get it to show up reliably except viamethods(+)
.)I did a
git bisect
, and it claims the problem showed up in commit 2c2d165, but this seems kinda random to me.The text was updated successfully, but these errors were encountered: