Encodable trait objects
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Monday Dec 15, 2014 at 10:30 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/19874
This issue was labelled with: A-an-interesting-project, E-hard in the Rust repository
<kmc> i want a world where I can send a Box<Encodable + FnOnce(A) -> B> across the network and call it on the other end
<Yurume> kmc: with a built-in AEAD protocol...
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
Begin with the earlier discussion in Rust issue #19874 and review the RFC repository's process. The issue does not name files, tests, or a concrete change; first establish a scoped proposal for Encodable trait objects and define what acceptance would mean before implementation work can be identified.
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
- 15/100