feat: a Method has a clearer definition (that passes strict type checking) #125
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
…king) Each "Method" now derives from a base class, that has a "get" function to get the internal tuple that controls its file's behaviour. This makes it possible for the same class to both have such a method, _and_ be callable to get a different method, which is how the current NO_COMPRESSION_* types work as methods but also as a callable to return a different method. (Maybe this can be turned into a Protocol in future changes)
michalc
force-pushed
the
feat/tighter-method-definition
branch
from
357dd7d to
05854ad
Compare
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.
Each "Method" now derives from a base class, that has a "get" function to get the internal tuple that controls its file's behaviour. This makes it possible for the same class to both have such a method, and be callable to get a different method, which is how the current NO_COMPRESSION_* types work as methods but also as a callable to return a different method.
(Maybe this can be turned into a Protocol in future changes)