Skip to content

regression 1.49: macro_rules unexpected tokens #79908

Closed

Activity

  1. added
    A-macrosArea: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
    on Dec 10, 2020
  2. added this to the 1.49.0 milestone on Dec 10, 2020
  3. added
    I-prioritizeIssue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}
    on Dec 10, 2020
  4. Aaron1011 commented on Dec 10, 2020

    @Aaron1011
    Contributor

    The fourier error looks like an old bug that was fixed by calebzulawski/fourier#17

  5. Mark-Simulacrum commented on Dec 10, 2020

    @Mark-Simulacrum
    MemberAuthor

    https://crates.io/crates/fourier only lists 0.1.0 so we should probably nag @calebzulawski about a point release one more time :)

  6. calebzulawski commented on Dec 10, 2020

    @calebzulawski
    Member

    Whoops, looks like I half-fixed it. One of my dependencies is too strict. It does look like the same error so probably not a regression...

  7. Mark-Simulacrum commented on Dec 11, 2020

    @Mark-Simulacrum
    MemberAuthor
  8. added
    E-needs-bisectionCall for participation: This issue needs bisection: https://github.com/rust-lang/cargo-bisect-rustc
    E-needs-mcveCall for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example
    on Dec 11, 2020
  9. added
    T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
    on Dec 11, 2020
  10. camelid commented on Dec 16, 2020

    @camelid
    Member

    @apiraino and I both feel unclear about this: Is this a Rust regression or a regression in a library that was then picked up by Crater?

  11. Mark-Simulacrum commented on Dec 16, 2020

    @Mark-Simulacrum
    MemberAuthor

    This is a regression in the Rust compiler.

  12. camelid commented on Dec 16, 2020

    @camelid
    Member

    The tiger error seems to me like fallout from implementing inline_const. I'm guessing the issue is that it's expecting a block but immediately gets a literal. Not sure how this is supposed to behave though.


    Reposting the error here:

    [INFO] [stdout] error: expected expression, found keyword `const`
    [INFO] [stdout]    --> src/ir.rs:481:23
    [INFO] [stdout]     |
    [INFO] [stdout] 347 |     (exp $e:expr) => {
    [INFO] [stdout]     |          ------- while parsing argument for this `expr` macro fragment
    [INFO] [stdout] ...
    [INFO] [stdout] 481 |             stmt!(exp const 1);
    [INFO] [stdout]     |                       ^^^^^ expected expression
    [INFO] [stdout] 
    [INFO] [stdout] 
    [INFO] [stdout] error: expected expression, found keyword `const`
    [INFO] [stdout]    --> src/ir.rs:482:23
    [INFO] [stdout]     |
    [INFO] [stdout] 347 |     (exp $e:expr) => {
    [INFO] [stdout]     |          ------- while parsing argument for this `expr` macro fragment
    [INFO] [stdout] ...
    [INFO] [stdout] 482 |             stmt!(exp const 2);
    [INFO] [stdout]     |                       ^^^^^ expected expression
    [INFO] [stdout] 
    [INFO] [stdout] 
    [INFO] [stdout] error: expected expression, found keyword `const`
    [INFO] [stdout]    --> src/ir.rs:483:23
    [INFO] [stdout]     |
    [INFO] [stdout] 347 |     (exp $e:expr) => {
    [INFO] [stdout]     |          ------- while parsing argument for this `expr` macro fragment
    [INFO] [stdout] ...
    [INFO] [stdout] 483 |             stmt!(exp const 3);
    [INFO] [stdout]     |                       ^^^^^ expected expression
    [INFO] [stdout] 
    [INFO] [stdout] 
    [INFO] [stdout] error: aborting due to 3 previous errors
    
  13. camelid commented on Dec 16, 2020

    @camelid
    Member

    But I'm not quite sure; the span seems potentially wrong.

  14. 18 remaining items

  15. removed their assignment
    on Dec 17, 2020
  16. camelid commented on Dec 17, 2020

    @camelid
    Member

    Actually, I just noticed that petrochenkov responded to my message asking for help finding the code 😄

  17. self-assigned this
    on Dec 17, 2020
  18. added 2 commits that reference this issue on Dec 18, 2020
    bd40604
    9269995
  19. camelid commented on Dec 18, 2020

    @camelid
    Member

    This should be fixed on the next nightly.

  20. Mark-Simulacrum commented on Dec 18, 2020

    @Mark-Simulacrum
    MemberAuthor

    Reopening to track beta fix.

  21. Mark-Simulacrum commented on Dec 27, 2020

    @Mark-Simulacrum
    MemberAuthor

    Should be backported to beta as part of #80417.

  22. camelid commented on Dec 29, 2020

    @camelid
    Member

    I think this can be closed as #80417 has been merged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

A-macrosArea: All kinds of macros (custom derive, macro_rules!, proc macros, ..)A-parserArea: The lexing & parsing of Rust source code to an ASTP-criticalCritical priorityT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.regression-from-stable-to-betaPerformance or correctness regression from stable to beta.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions