Type expressions should change with context
Open
prebug
- Dominant language
- C++
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
When a function or parameter is used in a valid, more-restrictive context, the node's type expression should reflect the matching type expression.
Each node should start as `TYPE_ARBITRARY` until a more restrictive type expression is enforced. Each node's type expression should be as generalized as possible for a given circumstance.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.