Consider making common traits object-safe
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
The following traits have Sized as a supertrait:
CloneDefaultFromFromStrInto
The bound on the first four can be moved from the trait to a method-level where clause, while the bound on Into can be removed entirely.
Doing this has the benefit of allowing otherwise object-safe traits to use these as a supertrait, but has the drawback of being a breaking change (albeit one that I doubt affects much code).
These other traits also extend Sized, but are unstable:
OneStepZero
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
Review the listed traits and the proposed changes to their Sized bounds, then assess the compatibility tradeoff described in the issue. Done means reaching and documenting a decision on whether these common traits should become object-safe, including the unstable traits mentioned.
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
- Clearly specified
- Newbie friendliness
- 25/100