-
Notifications
You must be signed in to change notification settings - Fork 25
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
Add support for fallible sanitizers ? #185
Comments
Uh. But to be honest, I have never thought of the use case like this before. |
Understandable 👌 Would you be open to proposals, I'd like to give it a try to see what it would require ? 🙂 (I have no clue if it's even possible I'm just curious 😁) |
I am not sure yet. The problem with that is that it will break the conceptual model that exists at the moment. Though, I don't wanna stop you from experimenting if you want to, I just don't feel committed to this at the moment. |
Do you have any other potential sanitization functions that could fail? |
Ok no problem 👌 I don't have any other fallible sanitization function in mind at the moment, if I find some I'll tell you |
I have a new type wrapping a
std:::fs::PathBuf
, I'd like for it to always be an absolute path.std::fs::canonicalize
does exactly that but is fallible (io::Result<Pathbuf>
).Is it feasible to add support for fallible sanitizers? Currently I can work around that limitation by unwraping it but I'm not a fan 😓.
The text was updated successfully, but these errors were encountered: