Update inotify dependency from 0.10.0 to 0.11.0 #35
Conversation
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
SoptikHa2
force-pushed
the
inotify-0.11
branch
from
5f2bf7d to
31a8079
Compare
|
Thanks for the quick review and for dealing with the linter output! |
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.
Source diff: hannobraun/inotify-rs@v0.10.2...v0.11.0
The breaking change noted from 0.10.2 to 0.11.0 is, “Make
bitsfield ofEventMask/WatchMaskinaccessible. You can use the.bits()method instead.”Since
deseddoesn’t use this field, no source-code changes are required. I verified thatcargo teststill passes.