Allow chaining of comparisons
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Namely for all comparison operators they should be allowed to be chained. The easy way of disambiguating them is since they are all binary operators just chain them with &&. Lastly, this can help with code clearness since the following can be avoided
let x = fn_long();
let y = fn_other();
if 5 < x && x < 10 && y <= x && 5 < y {
...
}
and replaced with:
if 5 < fn_other() <= fn_long() < 10 {
}
where the return values of any non_constant is held in reserve so that the function isn't called multiple times.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue body and evaluate the proposed comparison-chaining syntax, including the stated && interpretation and reserved return values for non-constant expressions. No files or tests are named; completion would require an agreed design for the Rust language change rather than a localized edit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100