Static Optimizations: Boolean Operators
Open
enhancement
- Dominant language
- C++
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Currently, if an Xita developer uses a boolean truth (a boolean expression that _**always**_ returns True or False) such as the following stub, it does the full calculation dynamically in assembly.
```haskell
1 && 2
3 || 0
```
This behavior is no good, because there is NEVER a situation where the above code isn't the same as the following:
```haskell
True
True
```
Boolean truths should be calculated and optimized into their final resting value within the Xita cross-compiler backend.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.