I have to agree with Stefan that this is turning into
bikeshedding [1].  My personal bias is towards `in`, probably due to
my many years of Python, but I am convinced that both keeping the
current duality or picking one of them will not lead to a mental
overload.  In fact, in order for us to stop spending brain cycles on
this, it would even seem sane to me to take the hash of the next
commit after this e-mail has been sent, apply modulo 10, if the number
is 1-3, preserve the status quo, for 4-6, switch to using `=`, for
7-9, switch to using `in`, for 0, discard the number and use the next
commit instead.

    Pontus

[1]: https://en.wikipedia.org/wiki/Parkinson's_law_of_triviality

Reply via email to