Re: Gradual 'tree' typing and C++
Project / Subsystem
gcc / gcc
Date
2026-07-22
Proposer
Richard Biener <richard.guenther@gmail.com>
Source type
public_inbox
Consensus
Proposed
Sentiment
—/10
Technical tradeoffs
- • Expressiveness vs. Verbosity: The proposed syntax might be more explicit but also more verbose and less flexible than current methods.
- • Maintainability: Debate over whether gradual typing, as implemented, improves or hinders code maintainability within the compiler's internal code.
- • Idiomatic C++ vs. Compiler Internals: Balancing standard C++ practices with the specific needs and existing patterns of compiler internal representations.
All attributes
- project
- gcc
- subsystem
- gcc
- patch_id
- —
- discussion_id
- CAFiYyc0sHsvi71mqZo3yRKRA+q2OUPYEpL9n9Qh+t+xVvjOeWA@mail.gmail.com
- source_type
- public_inbox
- title
- Re: Gradual 'tree' typing and C++
- headline
- Gradual 'tree' typing and C++
- tldr
- Discussion on C++ syntax for gradual typing in GCC's tree representation, with concerns about ugliness and verbosity.
- proposer
- Richard Biener <richard.guenther@gmail.com>
- consensus
- Proposed
- outcome
- proposed
- sentiment_score
- —
- technical_tradeoffs
-
- • Expressiveness vs. Verbosity: The proposed syntax might be more explicit but also more verbose and less flexible than current methods.
- • Maintainability: Debate over whether gradual typing, as implemented, improves or hinders code maintainability within the compiler's internal code.
- • Idiomatic C++ vs. Compiler Internals: Balancing standard C++ practices with the specific needs and existing patterns of compiler internal representations.
- series_id
- —
- series_role
- standalone
- series_parts
- []
- tags
-
- • gcc
- • compiler
- • type system
- • C++
- • gradual typing
- url
- https://inbox.sourceware.org/gcc/CAFiYyc0sHsvi71mqZo3yRKRA+q2OUPYEpL9n9Qh+t+xVvjOeWA@mail.gmail.com
- bugzilla_url
- —
- date
- 2026-07-22T00:00:00.000Z
Re: Gradual 'tree' typing and C++
Richard Biener critiques the proposed gradual ‘tree’ typing in C++ for GCC, citing concerns about ugly syntax, increased verbosity, and a less flexible approach compared to existing TREE_CODE mechanisms. The discussion highlights a preference for existing methods allowing varied coding styles over a rigid proposed syntax.