fs, File and Path API#264
Open
someotherself wants to merge 43 commits into
Open
Conversation
…t_file_access_layer_111
radumarias
requested changes
Dec 15, 2024
radumarias
requested changes
Dec 16, 2024
Closed
radumarias
requested changes
Dec 29, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #97
Implementation for:
crypto::fs_api::fs::OpenOptions
crypto::fs_api::fs::File (partial)
crypto::fs_api::fs (partial)
crypto::fs_api::path::Path.
crypto::fs_api::path::PathBuf.
Still on the to do list:
Check if crypto::fs_api::path::Path needs to be used as import in crypto::fs_api::async::fsFix parsing of path components so they don't leak (they use OsStr so far). May need our own Component struct and enumWill be resolved as a separate issue.Implement crypto::fs_api::io if neededFunctions implemented in fs: