Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No unsafe slicing #19901

Closed
cgaebel opened this issue Dec 16, 2014 · 5 comments
Closed

No unsafe slicing #19901

cgaebel opened this issue Dec 16, 2014 · 5 comments
Labels
A-collections Area: `std::collection` P-low Low priority

Comments

@cgaebel
Copy link
Contributor

cgaebel commented Dec 16, 2014

There's currently no version of slice, slice_from, slice_to, slice_mut, slice_from_mut, slice_to_mut, split_at that doesn't bounds check.

@kmcallister
Copy link
Contributor

Is this still the case? It seems like a pretty big oversight if we claim to have C-like performance.

Nominating P-high, not 1.0.

@cgaebel
Copy link
Contributor Author

cgaebel commented Jan 16, 2015

This appears to still be the case.

@kmcallister kmcallister added the A-collections Area: `std::collection` label Jan 16, 2015
@pnkfelix
Copy link
Member

P-low, not 1.0; tagging as wishlist.

@pnkfelix pnkfelix added P-low Low priority and removed I-nominated labels Jan 22, 2015
@nikomatsakis
Copy link
Contributor

This is easy to workaround, so it doesn't seem especially high priority, but it would be nice to have.

@steveklabnik
Copy link
Member

I'm pulling a massive triage effort to get us ready for 1.0. As part of this, I'm moving stuff that's wishlist-like to the RFCs repo, as that's where major new things should get discussed/prioritized.

This issue has been moved to the RFCs repo: rust-lang/rfcs#708

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-collections Area: `std::collection` P-low Low priority
Projects
None yet
Development

No branches or pull requests

5 participants