rust-lang / rust-lang/rfcs

Ability to pass ownership of unsized types

Open
#990 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

T-lang
Dominant language
Markdown
Stars
6.6k
Forks
1.7k
Avg merge
16h 14m
Merged PRs (30d)
1

Description

Currently you can't use unsized types as parameters or return values. There are good reasons to support this, including passing closures to fns and being able to write things like Rc::new(*slice) where slice has type Box<[T]> or what have you.

Postponed RFCs:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading this issue and the postponed RFC 977, which describes passing ownership of unsized types. Determine the remaining design questions and scope before proposing an updated RFC; done means the ownership semantics and supported parameter and return-value cases are specified and accepted through the Rust RFC process.

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
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.