More flexible operator overloading
Open
Nobody has claimed this yet.
A-operator
A-resolve
A-typesystem
postponed
T-lang
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
The current system ties the various operators to a specific trait. This can be limited, as some uses for the operators might not fit that trait. For example, the return type might be different than expected, or the methods might be unsafe.
Postponed RFCs along these lines:
- Ad-hoc operator overloading, which removes traits altogether: https://github.com/rust-lang/rfcs/pull/399
- Generic boolean operators, which extended return type for
==and friends beyondbool: #1008
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 by reading the issue's examples and the postponed RFCs for ad-hoc operator overloading and generic boolean operators. The work is not tied to a named file or test; done would require an agreed design for loosening operator traits, likely documented through an accepted RFC.
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
- Needs clarification
- Newbie friendliness
- 25/100