-
-
Notifications
You must be signed in to change notification settings - Fork 256
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
Getting "panic message is not a string literal" from Rust 2021 #505
Comments
I had to use |
I'm using Rust 2018 and I'm seeing the warning as well. It started with Rust 1.51.0, I think. |
Yep, this is a new rustc warning that we didn't realize was a problem in the emitted code before. |
(I won't have the bandwidth to make a PR to fix this anytime soon, likely, but I can approve a PR if someone else sets it up. I believe @01mf02 found where the issue needs fixing. |
This should be fixed by #507. |
this fixed by #507 |
If not too much of a problem, can we please get this in a release? I can continue to use |
When using Rust 2021 I am getting the following warning wherever
parses_to!
is used.The text was updated successfully, but these errors were encountered: