Lift restriction on terminal value types not modeling Expression
Open
Boost Review
- Dominant language
- C++
- Stars
- 108
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
- The value of a terminal cannot be another expression.
Is this a necessary restriction?
Not really; I probably put that restriction there due to lack of imagination. Terminals' values should be treated as simple types, but there's no real reason those types can't happen to model Expression.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.