Mike Gerwitz
963688f889
The token type was previously hard-coded to `UnknownToken`, since the use case was the beginning of the lowering pipeline at the start of the program, where there was no token type because the first parser (`XirReader`, currently) is responsible for producing the first token type. But when we're lowering from the graph (so, the other side of the lowering pipeline), we _do_ have token types to deal with. This also emphasizes the inappropriate coupling of `<XirReader as Iterator>::Item` with `ParsedResult`; I'd like to follow the same approach that I'm about to introduce with `tamec`, so see a future commit. DEV-13708 |
||
---|---|---|
.. | ||
tamec.rs | ||
tameld.rs |