Parse error with nested types about flux HOT 5 CLOSED

<< is also tokenized as a single token, but there's never (lexical) ambiguity for two <'s, they always have to be parsed as a left shift.

from flux.

Hmm looks like this has been around a while.

http://goto.ucsd.edu:8091/index.html#?demo=permalink%2F1671562719_503.rs

Perhaps to do with the Comma combinator? one can hack it by adding a junk , at the end like so, but rather gross...

#[flux::sig(fn () -> Option<Option<i32>,>)]
pub fn foo() -> Option<Option<i32>> {
    None
}

from flux.

Aargh... adding a blank works too, so probably some strange lexer oddness.

#[flux::sig(fn() -> Option< Option<usize> >)]

from flux.

Yeah, this has been there for a while. >> is tokenized as a single token. One possible solution is to split it into two tokens and put it back together when parsing a right shift operator. Not sure if lalrpop has support for this.

from flux.

from flux.