Add ability to use fuse-mt without the path translation #45
Conversation
This file contains 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
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.
Hi! First of all: thanks for writing this awesome library.
I'm writing a filesystem at the moment and wanted to make use of fuse-mt but the concept of tracking paths doesn't really make sense for my usescase so I've added the ability to instead receive inodes from fuse-mt. This should solve e.g. #21
There is a breaking changed I could not avoid:
impl FilesystemMT for Foohas to becomeimpl FilesystemMT<'_> for Foonow. Which is why I've also decided to bump the minor version.I've also bumped the fuser version to 0.14 and added a new example for the new type of "unmanaged" FilesystemMT.
I've designed most other changes to not break any APIs further which has resulted in
RawFileAttrimplementingDerefandDerefMutwith FileAttr as a target.