-
Notifications
You must be signed in to change notification settings - Fork 736
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
Adding 2 new decoders: #1196
Adding 2 new decoders: #1196
Conversation
The documentation is not available anymore as the PR was closed or merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding this!
assert Strip(left=0, right=0) is not None | ||
assert isinstance(Strip(left=0, right=0), Decoder) | ||
assert isinstance(Strip(left=0, right=0), Strip) | ||
# assert isinstance(pickle.loads(pickle.dumps(Strip(left=0, right=0))), Strip) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here, to remove or fix?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hoped it would go unoticed :)
Pickling is a nice touch, but cumbersome.
- Fuse will simply concatenate all tokens into 1 string - Strip will remove n char from left or right Sequence(Replace("_", " "), Fuse(), Strip(1, 0)) should be what we want for the `Metaspace` thing. - Note: Added a new dependency from better parsing of decoders. This is due to untagged enums which can match anything the `MustBe` ensure there's no issue between Fuse and ByteFallback. Since both are new the chances for backward incompatibility is low.
597017e
to
c943c35
Compare
Sequence(Replace("_", " "), Fuse(), Strip(1, 0)) should be what we want
for the
Metaspace
thing.This is due to untagged enums which can match anything the
MustBe
ensure there's no issue between Fuse and ByteFallback.
Since both are new the chances for backward incompatibility is low.