Repository navigation
.immutable or .mutable? #10
Description
Generally I try to make my boolean options and properties positive. Arguably, immutable is the negation of mutable. Following that principle, then, the getter should be spelled mutable, and to check for immutability you'd negate the result.
I don't feel strongly about this, but it's something to think about.
Activity
phoddie commentedon Oct 16, 2024
A nice side effect of
immutableis that engines which don't implement this property will give the expected result for......since since
immutablewill beundefined.gibson042 commentedon Oct 16, 2024
Right; there's a tension here between "booleans should default to false" (which favors
immutable) and "booleans should be named with positive polarity" (which favorsmutable). I'm fine either way, but more inclined towardsimmutable.erights commentedon Dec 23, 2024
At the December tc39 meeting, we got agreement on
.immutable. Since that is consistent with the current state of this repo, I'm closing this as resolved.