Lucas Kramer

Terminal patterns would be nice to have for #321 - see Ted's comment there. The terminal pattern syntax should probably also include the location, but I don't think the type...

Yeah, I think that's correct for primitives. Lists aren't really a primitive, though, as they are more like a nonterminal type (they are sort of pretending to be one...) so...

Basically, we want to be able to pattern match on terminals. Currently this is a bug in the `silver:compiler:metatranslation` library where we are emitting wildcards instead of terminal patterns, and...

Note that `import ... only ...` doesn't affect whether or not things get imported, it only controls whether their short name gets put in the env. In your example, the...

I would prefer that we only do this for names that are actually java keywords. We would need to append something to the offending component of the java package name,...

Would it be reasonable to consider adding a second type of semantic action for terminals that *is* run as soon as the terminal is scanned? This is the behavior that...

So I found a reason why we don't want to simply change the behavior of semantic actions on layout terminals to be scanner actions instead of parser actions - we...

Would it at least be possible to have a way of suppressing the 'useless nonterminal' warnings that show up in situations like this? This is kind of annoying, and currently...

Yes - in ableC we build several parsers on various nonterminals (`Expr_c`, `Decl_c`, etc.) in the concrete syntax as part of a helper library for constructing ASTs. Since all these...

Seems like a reasonable plan. IIRC, this was the idea behind the `compile` driver but that never got finished. I don't think I would have time to work on this...