rust-lang / rust-lang/reference
[paths.expr.argument-order] is outdated
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 607
- PR merge metrics
- PR metrics pending
Description
The order of generic arguments is restricted to lifetime arguments, then type arguments, then const arguments, then equality constraints.
const and type arguments can now be in arbitrary order. This is already correct for parameters https://doc.rust-lang.org/nightly/reference/items/generics.html#r-items.generics.syntax.decl-order. This restriction generally shouldn't exist. We parse generic arguments in arbitrary order and only error when checking whether the order matches the generic parameters of the item
Contributor guide
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 paths.expr.argument-order section and compare its restriction with the linked Rust Reference generics syntax. Update the outdated statement so it reflects arbitrary ordering of const and type arguments, then verify the surrounding documentation remains consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100