-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Certain unicode character combinations make the compiler angry #5272
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
Comments
The backtrace from rust_task_fail would be informative. |
Of course. I assume it's all the gumpf that comes out of RUST_LOG=rustc=1,::rt::backtrace Here we go:
|
I actually meant the gdb backtrace from a breakpoint at rust_task_fail. |
Oh. I'll see what I can do about that over the next couple of days - I've not played with GDB in some time. |
OK, not sure if this is what you were after:
I'm kinda in alien territory here. Do I need to compile Rust with debug symbols or anything to make that useful to you? |
No, this output is the best you can get right now. Thanks! |
And entertainingly enough, it actually shows us that emitting certain warnings about unused variables is triggering assertions when providing the extra data required. |
Is this related to #4780? |
It does look to be a duplicate, as the APL glyphs I'm using are multibyte. |
Closing as dup of #4780 -- reopen if it turns out not to be :-) |
add lint on File::read_to_string and File::read_to_end Adds lint `verbose_file_reads` which checks for use of File::read_to_end and File::read_to_string. Closes rust-lang/rust-clippy#4916 changelog: add lint on File::{read_to_end, read_to_string}
So, I have the following
And for some reason, on both my OSX build of Incoming, and my on my Ubuntu build of it, I get an error:
When I start using the variables (such as sticking Print statements after each definition of it) it compiles fine. Taking out the weird APL symbols that my interpreter is going to be testing also fixes it.
Is there an issue with having too many unused instances of a variable? Or with trouble with (super obscure) Unicode glyphs?
The text was updated successfully, but these errors were encountered: