impl dyn Any for monomorphized dyn Trait
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
there's no reason why stuff like this shouldn't be made more friendly and optimized (I shouldn't need two boxes for it to work): https://play.rust-lang.org/?version=stable&mode=debug&edition=2015&gist=7281cea78856a6bc6c8693dcb320b9d0
note that I'm talking specifically about fn<T: Foo>(t: T) -> Box<dyn Any> kinda usage. you wouldn't be able to take an arbitrary dyn Foo and turn it into an dyn Any (yet).
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 linked Rust playground example and the stated generic dyn Trait to Box<dyn Any> usage; no repository file or test is identified. Done would require a decided and documented approach that addresses the requested behavior and the limitation around arbitrary dyn Foo conversions.
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