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.

Sign up for GitHub

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

Jump to bottom

Path::new should return Option<Path> vs. failing (if there is a null byte) #14048

Closed
carllerche opened this issue May 8, 2014 · 2 comments
Closed

Path::new should return Option<Path> vs. failing (if there is a null byte) #14048

carllerche opened this issue May 8, 2014 · 2 comments

Comments

@carllerche
Copy link
Member

Failing prevents using Path::new in an embedded scenario (not wrapped in a task).
@Ryman
Copy link
Contributor

Ryman commented May 10, 2014

Path::new_opt exists for this?

http://static.rust-lang.org/doc/master/std/path/trait.GenericPath.html#method.new_opt

@aturon aturon mentioned this issue Nov 6, 2014
Closed
10 tasks
@japaric japaric mentioned this issue Nov 19, 2014
Merged
@steveklabnik
Copy link
Member

Given that rust-lang/rfcs#474 has landed, this would need another RFC to change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@carllerche @steveklabnik @Ryman