Consider expanding `SyntaxItemList<T>` and `SeparatedSyntaxItemList<TElement, TSeparator>` API surface about celerity HOT 2 CLOSED

Somewhat related: LeadingTrivia and TrailingTrivia on SyntaxToken should probably be changed to SyntaxItemList<SyntaxTrivia>.

from celerity.

This begs the question, though: Should we also expose GetText() and GetFullText()? That would require a Parent property. But then that might signal that the list is a node in the tree, which is not actually the case. We'd then also have to consider tree traversal methods, at which point these lists start to look an awful lot like SyntaxItems in their own right...

Decision: Tree property, Parent property, Span/FullSpan properties, ToString()/ToFullString() methods, GetText()/GetFullText() methods. No tree traversal methods. In the future, we could consider extracting these into an interface if there's a use case for that.

(I think this will also allow us to reduce the amount of SetParent() calls we emit in generated node classes.)

from celerity.