Improvements for bitwise, logical and comparison operators #6
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.
1 ^ 2 ^ 3
works now.Logical operators (or, and) only evaluate the second argument if necessary (short-circuiting). This also works with truthiness.
You can see examples for these things in the tests I added.
I am currently working on comparisons, there is a lot missing (e.g. comparison of bools, lists, strings, equality of sets and lists). I think it would be best to base it on the methods
__eq__()
etc., but that would require some work.Also, chained comparison is not supported yet (e.g.
1 < 2 < 3 > 0
). I am thinking about it, but it's not really straight-forward to implement.Generators, list/generator/tuple comprehensions, and splat/star-args are waiting as well, so there is enough to do :D
Matthias