Statically-sized stack strings
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Sometimes, some specialists strive to store strings stackwise. Sadly, one's stock in stack strings is shot down on stable. See, in spite of 'static strings storing size statically, they're symbolised solely as a slice. So what service should stack-stored strings serve? Scrutinise surely:
const fn splice<
const SOURCE_A: &str,
const SOURCE_B: &str,
>() -> StaticStr<SOURCE_A.len() + SOURCE_B.len()> {
let mut scratch = [0u8; SOURCE_A.len() + SOURCE_B.len()];
// ...
StaticStr::new(scratch).unwrap() // Surity of success
}
const SALUTATION: &str = "Hello";
const SPOT: &str = "world";
const SPLICED_STRING: &str = &splice::<SALUTATION, SPOT>();
"Simply store a slice", you shout. A slice from splice's scope survives not the 'static span! Sure, &'static str supplying splice solves this specific strait, but stack strings support spawning several services for &'static strs.
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
The issue proposes statically sized stack strings and gives a Rust example using splice and StaticStr, but names no files, tests, or implementation entry point. Start by clarifying the intended feature and its scope; completion criteria are not specified in the issue.
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