trap invalid opcode about lalrpop HOT 2 CLOSED

Woah. Let me check it out.

from lalrpop.

Ah, I think this is a duplicate of #32. The problem has to do with this:

Prec2 = {
  r".*" => { <>.to_string() }
};

I need to figure out what is going on here, but this is surely not going to work for you in any case. The problem is that LALRPOP operates on a two-stage tokenize-and-then-parse model, and here you have specified a token of "._". This will surely conflict with all the other tokens (e.g., r"[-+]?[0-9]_.?[0-9]+"). In other words, the way that LR(1) parsers work, the generated code must first (unambiguously) decide which regular expression the text belongs to, without consider where we are in the grammar. (It might be interesting, though, to add a PEG mode, which would accept things like this, or perhaps some other similar hybrid.)

from lalrpop.