Proposal: Allow optional `type` keyword in generic
Open
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
We have 3 kinds of generic parameters at present : type, lifetime and const value.
struct GenericType<T, 'a, const U> {}
Lifetime and const value starts with significant obvious punctuation and keyword, but normal type does not.
I'm proposing to allow type keyword in this situation.
// Multiply kinds of generic parameters involved
struct GenericType<type T, 'a, const U> {}
// only type parameter involved
struct GenericType<T1, T2> {}
Is there anybody agree with me that this may be clearer?
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 proposed generic-parameter syntax in this issue and review the repository's RFC process; no implementation files or tests are named. Done would require a resolved proposal and accepted RFC direction for allowing an optional type keyword, rather than a localized code change.
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