Stream: t-compiler/rust-analyzer

Topic: unexpected token in input


Eh2406 (Dec 07 2020 at 15:51, on Zulip):

I just updated my rust analyzer, and now every file (at least in this project) gets the error unexpected token in input is it happening to other people?

Jonas Schievink [he/him] (Dec 07 2020 at 15:52, on Zulip):

Can you provide more details? It's probably a combination of a bug in macro expansion and diagnostics reporting

Eh2406 (Dec 07 2020 at 15:53, on Zulip):

The project is https://github.com/pubgrub-rs/pubgrub

Eh2406 (Dec 07 2020 at 15:54, on Zulip):

image.png

Eh2406 (Dec 07 2020 at 15:55, on Zulip):

Win 10.

Eh2406 (Dec 07 2020 at 15:55, on Zulip):

VSCode with rust analizere, just updated.

Eh2406 (Dec 07 2020 at 15:59, on Zulip):

What more would be useful?

Jonas Schievink [he/him] (Dec 07 2020 at 16:02, on Zulip):

It would be good to know which macro invocation causes this

Jonas Schievink [he/him] (Dec 07 2020 at 16:03, on Zulip):

But I can see how that might be hard to figure out, heh

Laurențiu (Dec 07 2020 at 16:03, on Zulip):

I can reproduce it

Laurențiu (Dec 07 2020 at 16:05, on Zulip):

It's the proptest! block at the bottom

Laurențiu (Dec 07 2020 at 16:07, on Zulip):

Minimizing https://github.com/AltSysrq/proptest/blob/master/proptest/src/sugar.rs#L150-L248 is left as a homework

Eh2406 (Dec 07 2020 at 16:08, on Zulip):

Should I open an issue, or have you built a more minimal example?

Laurențiu (Dec 07 2020 at 16:11, on Zulip):

You can probably file it like this with a mention that the proptest! block is causing it.

Last update: Jul 27 2021 at 22:15UTC