This has been closed for more than 2 weeks. There were, literally, no comments from the user base during the "request for feedback" period before it was submitted. There was one request after it was submitted to simply roll it back. But, other than that, there has been literally no feedback on this thread from people who might be affected - until your post, 2+ weeks after this was submitted.
I am not automatically opposed to adding a new operator. "~=" looks like the "modify and assign" operators. So:
is like
which might lead one to think that
would be syntactic sugar for
except "~" is a unary operator, so obviously not.
I can see using
to mean "a is sort-of equals to b", except, the way you say you WANT to use it - simply replacing every instance of "==" with "~=" tells me that that is not, in fact, how you intend to use it. You intend to simply replace every single instance of "==" with "~=" - whether or not you really require the new semantic - out of pure laziness, rather than using the new operator exactly when you need the new semantic.
Can't say I feel motivated to spend my precious time to enable that.