The current checkparse tests are getting unwieldy. Writing the tree to
match against is a bit of a pain. It would be nice to introduce a
builder API similar to the Roslyn "quoter" API. This
allows building more complex trees part by part and stubs in tokens
when trees are not being directly backed by source. This would be
useful when creating replacement trees in a syntax transformation.
The current checkparse tests are getting unwieldy. Writing the tree to match against is a bit of a pain. It would be nice to introduce a builder API similar to the Roslyn "quoter" API. This allows building more complex trees part by part and stubs in tokens when trees are not being directly backed by source. This would be useful when creating replacement trees in a syntax transformation.