# Proposal: Grammar Working Group

**URL:** <https://internals.rust-lang.org/t/proposal-grammar-working-group/8442>\
**Category:** compiler\
**Created:** [September 21, 2018, 2:34am UTC](https://internals.rust-lang.org/t/proposal-grammar-working-group/8442 "2018-09-21T02:34:55Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![matklad](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/matklad/32/12266_2.png) [@matklad](https://internals.rust-lang.org/u/matklad)\
**Post date:** [September 21, 2018, 7:39pm UTC](https://internals.rust-lang.org/t/proposal-grammar-working-group/8442/26 "2018-09-21T19:39:20Z")

</div>

> [@eternaleye](#):
>
> Notably, an indented-tree serialization is only viable for a CST or AST in this taxonomy; it would not be sufficient for cases where the parse tree is needed, such as making sure that diagnostics report ranges correctly.

Hm, why is this so?i think you can serialize parse trees just fine? The example from libsyntax2 is a parse tree

---

_[View the full topic](https://internals.rust-lang.org/t/proposal-grammar-working-group/8442)._