rust-lang / rust-lang/rfcs

[UR] local storage inside function

Open
#795 0 comments 0 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

Issue by nicolasboulay
Wednesday Jan 22, 2014 at 16:39 GMT

For earlier discussion, see https://github.com/rust-lang/rust/issues/11726

This issue was labelled with: I-enhancement in the Rust repository


It could be great to have local storage that are unique by function call site (like Lustre does).

This reduce the need for dynamique memory and it's much easier than doing it by hand. This is also great for real time application, or application that refuse dynamic memory (for security, safety or speed reason).

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 reviewing the earlier discussion in rust-lang/rust issue 11726 and the repository's RFC process. Clarify the proposed function-call-site local storage semantics and determine what an accepted RFC would need to specify before implementation can begin.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.