Create an empty "Primitive" trait implemented by primitive (and only primitive) types to improve inferring "as" availability in generics
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
I've been trying to do something along the lines of:
fn foo<T> (buffer: &[u8]) {
let foo: T = SomeTValue();
&[0..foo as usize]
}
And discovered that as won't work there and there seems to be no way to add a 'where' bound to the T type to make sure the compiler accepts "as" here knowing that it'll work because it cannot infer that T is a primitive type.
Having a trait that allows <T: Primitive> type bounds would be handy here to let the compiler know that the code should work.
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 generic example in the issue and examine how Rust's as expressions and generic bounds currently handle primitive types. No source files, tests, or entry points are identified; done would require a settled design for a Primitive bound that is implemented only by primitive types and supports the intended generic cast.
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
- 28/100