Re: Gradual 'tree' typing and C++
Project / Subsystem
gcc / gcc
Date
2026-07-21
Proposer
Jakub Jelinek <jakub@redhat.com>
Source type
public_inbox
Consensus
Proposed
Sentiment
—/10
Technical tradeoffs
- • Static typing and safety vs. dynamic typing flexibility and verbosity.
- • Readability and maintainability of compiler code.
- • Ergonomics for developers working with internal data structures.
All attributes
- project
- gcc
- subsystem
- gcc
- patch_id
- —
- discussion_id
- amAAuEOmSKNh-_kZ@tucnak
- source_type
- public_inbox
- title
- Re: Gradual 'tree' typing and C++
- headline
- Gradual 'tree' typing and C++
- tldr
- Concerns raised about the syntax and verbosity of gradual typing proposals for GCC's internal tree representation.
- proposer
- Jakub Jelinek <jakub@redhat.com>
- consensus
- Proposed
- outcome
- proposed
- sentiment_score
- —
- technical_tradeoffs
-
- • Static typing and safety vs. dynamic typing flexibility and verbosity.
- • Readability and maintainability of compiler code.
- • Ergonomics for developers working with internal data structures.
- series_id
- —
- series_role
- standalone
- series_parts
- []
- tags
-
- • gcc
- • compiler internals
- • c++
- • type system
- bugzilla_url
- —
- date
- 2026-07-21T00:00:00.000Z
Re: Gradual 'tree' typing and C++
Jakub Jelinek expresses strong reservations about a proposal for gradual typing in GCC’s internal tree representation. He argues that the proposed syntax is ugly, more verbose than necessary, and restricts the flexibility developers currently have when working with TREE_CODEs and similar macros.