"when" function syntax for traits
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Currently, you can have this:
struct X<T> {
x: T
}
impl<T> X<T> {
fn a(self) -> T {
self.x
}
}
impl X<String> {
fn b(&self) -> String { // doesn't exist in X<T> unless T: String
self.x.clone()
}
}
But if you have a trait, you can't have this:
trait X<T> {
fn a(self) -> T;
}
trait X<String> {
fn b(&self) -> String;
}
So I propose the following syntax, for methods that are only available if certain generic type constraints are met:
trait X<T> {
fn a(self) -> T;
fn b(&self) -> String when T = String; // or T: Traits
fn c<U>(&self) -> &[U] when T = Vec<U>;
}
Then an impl would have to provide b or c if and only if T can be one of String or Vec, respectively.
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 generic impl and trait examples in the issue, then examine the proposed when constraints and the requirement that implementations provide methods conditionally. There are no files or tests named; done would require a settled language design and an accepted resolution for the proposed trait syntax.
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