rust-lang / rust-lang/rfcs

Allow chaining of comparisons

Open
#2,083 17 comments 40 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

T-lang
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.