Anyway to have a priority?

[lemonlambda]

Like this for example

plex::parser! {
    fn parse_(Token, Span);

    // combine two spans
    (a, b) {
        Span {
            lo: a.lo,
            hi: b.hi,
        }
    }

    program: Program {
        statements[s] => Program { stmts: s }
    }

    statements: Vec<Expr> {
        => vec![],
        statements[mut st] outer[e] SemiColon => {
            st.push(e);
            st
        }
    }

    outer: Expr {
        #[priority]
        Token SemiColon => ...,
        inner[a] => a,
    }
    
    inner: Expr {
        Token => ....,
    }
}

[lemonlambda]

@goffrie

[maxrdz]

Requesting the same feature here, as I'm dealing with some issues in my grammar which could be solved with priority.

[goffrie]

Yes, there's the #[overriding] attribute that gives a rule precedence over other rules. There isn't any syntax for multiple priority levels but it is supported in the underlying LALR(1) library so it should be simple enough to add.

[maxrdz]

By 'it should be simple to add' are you referring to implementing it on the crate, or simple to add on the user's end by using the LALR crate directly? I see there is a #[overriding] attribute (even though I can't find docs on it) but it doesn't seem to apply any sort of precedence over other rules.

[goffrie]

I mean simple to add to this crate.

…

On Fri, Sept 29, 2023, 00:51 Max Rodriguez ***@***.***> wrote: By 'it should be simple to add' are you referring to implementing it on the crate, or simple to add on the user's end by using the LALR crate directly? I see there is a #[overriding] attribute (even though I can't find docs on it) but it doesn't seem to apply any sort of precedence over other rules. — Reply to this email directly, view it on GitHub <#51 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJO2TRIG47356OHKL3SEIDX4Z4WTANCNFSM6AAAAAA5MCLWTY> . You are receiving this because you were mentioned.Message ID: ***@***.***>