Skip to content
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

Unrecognized literal c"" #517

Open
mleonhard opened this issue Apr 19, 2024 · 1 comment · May be fixed by #518
Open

Unrecognized literal c"" #517

mleonhard opened this issue Apr 19, 2024 · 1 comment · May be fixed by #518

Comments

@mleonhard
Copy link

Cargo-geiger 11.7 crashes when it encounters Rust code that uses C-style string literals which were introduced in Rust v1.77.

user@Users-MBP build-data % cat Cargo.toml               
[package]
name = "build-data"
repository = "https://gitlab.com/leonhard-llc/ops"
...
user@Users-MBP build-data % git show |head -n 1
commit 6f99a63717effa72a9bfc2d950c8614cafab9b5d
user@Users-MBP build-data % ~/.cargo/bin/cargo-geiger
cargo-geiger 0.11.7
user@Users-MBP build-data % ~/.cargo/bin/cargo-geiger
...
{"$message_type":"artifact","artifact":"/Users/user/ops/target/debug/deps/libtest_set_git_commit-b34cd715ff6be484.rmeta","emit":"metadata"}
    Finished dev [unoptimized + debuginfo] target(s) in 5.88s
thread '<unnamed>' panicked at /Users/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/syn-1.0.109/src/lit.rs:1020:13:                                    
Unrecognized literal: `c""`
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
user@Users-MBP build-data % RUST_BACKTRACE=1 ~/.cargo/bin/cargo-geiger
{"$message_type":"artifact","artifact":"/Users/user/ops/target/debug/deps/libtest_set_source_date-9f40d682582364bb.rmeta","emit":"metadata"}
    Finished dev [unoptimized + debuginfo] target(s) in 8.17s
thread '<unnamed>' panicked at /Users/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/syn-1.0.109/src/lit.rs:1020:13:                                    
Unrecognized literal: `c""`
stack backtrace:
   0: _rust_begin_unwind
   1: core::panicking::panic_fmt
   2: syn::lit::value::<impl syn::lit::Lit>::new
   3: syn::parse::ParseBuffer::step
   4: <syn::lit::Lit as syn::token::Token>::peek::peek
   5: syn::token::peek_impl
   6: syn::expr::parsing::trailer_expr
   7: syn::expr::parsing::unary_expr
   8: syn::expr::parsing::<impl syn::parse::Parse for syn::expr::Expr>::parse
   9: syn::punctuated::Punctuated<T,P>::parse_terminated_with
  10: syn::expr::parsing::trailer_helper
  11: syn::expr::parsing::trailer_expr
  12: syn::expr::parsing::unary_expr
  13: syn::expr::parsing::expr_early
  14: syn::stmt::parsing::stmt_expr
  15: syn::stmt::parsing::parse_stmt
  16: syn::stmt::parsing::<impl syn::stmt::Block>::parse_within
  17: syn::item::parsing::parse_rest_of_fn
 18: syn::item::parsing::<impl syn::parse::Parse for syn::item::Item>::parse                                                                                        
  19: syn::file::parsing::<impl syn::parse::Parse for syn::file::File>::parse
  20: syn::parse::Parser::parse_str
  21: syn::parse_file
  22: geiger::find::find_unsafe_in_string
  23: geiger::find::find_unsafe_in_file
...
@pinkforest
Copy link
Collaborator

Great find - would you like to send a PR ?

thanks very much for raising the issue

@mleonhard mleonhard linked a pull request Apr 19, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants