-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
ICE: Type metadata for unique id '{&{&[]{struct c5265340fd5e95cf/2157e}}}' is already in the TypeMap! #14895
Comments
closing as duplicate of #14871. Note that there is a workaround described by @michaelwoerister in his discussion with nick: #14819 (comment) (I have been considering landing this workaround since I imagine this is going to bite a lot of people, at least those who like using |
Felix, if you'd like to commit the workaround to master, please just go ahead. In the future, I'll make things like this a warning. Not all bugs warrant aborting the program... On June 14, 2014 5:03:33 PM CEST, Felix S Klock II [email protected] wrote:
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
(just for those following along the conversation: michael ended up posted that workaround as PR #14909 .) |
Since that PR got closed, should this be reopened? I can still reproduce it. EDIT: Nevermind, I got confused by the continued conversation here. |
…r=Veykril fix: don't try determining type of token inside macro calls When we're requested `Go to Type Definition`, we first downmap the token in question to tokens in every macro call expansion involved, and then determine the type of those mapped tokens by looking for the nearest ancestor node that is either expression or pattern (or a few others). This procedure has one flaw: When the downmapped token is inside another macro call, the nearest ancestor node to retrieve the type of is *that* macro call. That's not what we should return in general and therefore we should disregard it. Notably, now that we expand built-in `format_arg!` and its family macros, we're always returning [`Arguments`] when one `Go to Type Definition` at `dbg!(variable$0)` along with the actual type of `variable` without this patch. [`Arguments`]: https://doc.rust-lang.org/nightly/core/fmt/struct.Arguments.html
My Travis CI builds started failing yesterday for a few very simple programs. Here's a sample:
Here's the compiler version I'm using:
Here's the output:
Note that this just started happening last night, and occurs for a number of small programs - see sample output here.
The text was updated successfully, but these errors were encountered: