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
2/10
Technical tradeoffs
- • Increased code verbosity and complexity for developers.
- • Potential for compile-time type safety vs. runtime checks.
- • Impact on developer productivity and code maintainability.
All attributes
- project
- gcc
- subsystem
- gcc
- patch_id
- —
- discussion_id
- 8b074ff81c6cd18c313d7f46626922c9e1aa9b62.camel@gwdg.de
- source_type
- public_inbox
- title
- Re: Gradual 'tree' typing and C++
- headline
- Gradual 'tree' typing and C++
- tldr
- Reviewers critique a gradual typing proposal for GCC's tree representation, calling it an 'abomination' that makes developers' lives harder.
- proposer
- Jakub Jelinek <jakub@redhat.com>
- consensus
- Proposed
- outcome
- proposed
- sentiment_score
- 2
- technical_tradeoffs
-
- • Increased code verbosity and complexity for developers.
- • Potential for compile-time type safety vs. runtime checks.
- • Impact on developer productivity and code maintainability.
- series_id
- —
- series_role
- standalone
- series_parts
- []
- tags
-
- • gcc
- • compiler internals
- • c++
- • type system
- • ergonomics
- bugzilla_url
- —
- date
- 2026-07-21T00:00:00.000Z
Re: Gradual 'tree' typing and C++
This discussion follows an exchange about gradual typing in GCC’s internal tree representation. Arsen Arsenović suggested converting checks into fallible conversion functions (e.g., try_as_tree_or_whatever). Jakub Jelinek strongly disagreed, calling it an improvement. Eric Botcazou concurs with Jelinek, expressing dismay that the transition to C++ has led to such ‘abominations’ and arguing it makes compiler development harder.