Interaction between elision and trait objects is not ideal
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
As observed on https://github.com/rust-lang/rust/pull/27248, the interaction between elision and trait objects changed recently as the result of a bug fix, but in some cases the older, buggy behavior may have been preferable. In particular, trait object defaults operate by different rules per RFC 599. I have also argued that object lifetime defaults ought to be treated differently from other lifetimes for the purpose of '_, which is closely tied to elision. However, it's unclear just what the new rules ought to be.
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 behavior change discussed in rust-lang/rust#27248, then compare RFC 599 with the RFC 1177 comment about object lifetime defaults and '_. The issue is done only when the intended elision and trait-object rules are clearly decided and documented, likely 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