Strict value is not null coalesced from a false value #29
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.
Resolves #28 (Strict value can't be null coalesced from a false value)
Background
Ruby's conditional assignment operator (
||=
) is typically used for assigning default values to variables:However, it has an issue with boolean values:
If
false
is passed to some_method, the conditional assignment operator will treatfalse
exactly the same asnil
. As a result, boolean variables must be given default values differently from other types of values:Proposed Standard: Boolean Attributes With Default Value
Messaging Handle has an boolean attribute
strict
, which has a default value:This is a mistake, since the conditional assignment operator can't be used with boolean value. Instead, we propose the following:
This proposed standard follows the existing norm for how default boolean values are assigned to local variables in methods.