Support for generic type parameters about lalrpop HOT 7 CLOSED

This is already supported, in fact. You do it by adding the type parameters to the grammar declaration, like so:

grammar<F:Factory>;

from lalrpop.

Ah, actually, I think bounds have to be written as where clauses:

grammar<F> where F: Factory;

Anyway, let me know how that works for you. I don't know that I've tested this functionality very thoroughly, as I myself have not yet had a user for it.

from lalrpop.

I began to port my grammar from rust-peg to Lalrpop. So far I hit the following problems;

1. The 'input lifetime comes after the F type parameter.

  pub fn parse_Term<
      F,
      'input,
  >(
      input: &'input str,
  ) -> Result<i32, __ParseError<usize,(usize, &'input str),()>> where
    F: ParserFactory,
  {...}

This is true not just for functions, but for impls:

impl<F, 'input, > __ToTriple<F, 'input, > for Result<(usize, (usize, &'input str), usize),()> {...}

2. The generic type parameters are not propagated:

   __state0(...)
   

   instead of

   __state0::<F>(...)
   

from lalrpop.

OK, I think I fixed that problem, thanks for the report!

from lalrpop.

(You'll have to use the git version for now though.)

from lalrpop.

Note the new test case:

https://github.com/nikomatsakis/lalrpop/blob/ae027da57edd1b52ebd935e1af0011b5c683ecea/lalrpop-test/src/expr_generic.lalrpop

from lalrpop.

Thanks!

from lalrpop.