Fix str() bug for tuple values #33
Merged
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
Replaced the use of old-style formatting strings in __str__ methods.
At first, that seems like a dated but harmless practice, but unfortunately
While dated and seemingly a harmless practice, OSlash actually uses it
in an incorrect way.
If a program using OSlash deals with types other than strings, then the
__str__ methods for classes like `Left`, `Right`, and `Either`, OSlash
directly writes:
return '%s' % value
where `value` is an arbitrary type.
Unfortunately, '%s' % value is only guaranteed to work if the value
is a string, since Python will not call `str()` on it.
(Well, more precisely, `'%s' % value` is guaranteed to *fail* if the
value happens to be a tuple of a certain kind, since Python will try
to unpack the tuple into the string formatting operation)
The upshot is that such programs will get TypeErrors. Instead, use
Python 3.8+ f-strings to guarantee that the value is converted to a
string.
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Replaced the use of old-style formatting strings in str methods.
At first, that seems like a dated but harmless practice, but unfortunately
While dated and seemingly a harmless practice, OSlash actually uses it in an incorrect way.
If a program using OSlash deals with types other than strings, then the str methods for classes like
Left,Right, andEither, OSlash directly writes:where
valueis an arbitrary type.Unfortunately, '%s' % value is only guaranteed to work if the value is a string, since Python will not call
str()on it.(Well, more precisely,
'%s' % valueis guaranteed to fail if the value happens to be a tuple of a certain kind, since Python will try to unpack the tuple into the string formatting operation)The upshot is that such programs will get TypeErrors. Instead, use Python 3.8+ f-strings to guarantee that the value is converted to a string.