We would need a really really compelling reason to use ==. I'd prefer a less concise solution even if == is strictly speaking the best tool for the job. Or, at least, the comment "// not a bug" with enough use-case explanation to destroy the concision benefits of == in the first place. I thought the linter forbase == anyway.