Will the "custom == operator" problem be addressed at some point?

https://blogs.unity3d.com/2014/05/16/custom-operator-should-we-keep-it/

I remember reading this blog post back in the day, and it instantly sent me searching for alternatives to Unity, because the fact that Unity was willing to sacrifice performance to such an extent just seemed baffling to me. Even to this day, it still gives me nightmares, and every time I tell my colleagues about it, their faces turn pale.

So I was wondering.... will it be fixed as part of the scripting upgrades? Can it at the very least become an option?

 

I would also appreciate the option not to use the custom == operator.

- S.

 

We have not made decision on this yet. Once we do, we will be sure to communicate the change.

See existing discussion. https://forum.unity3d.com/threads/unity-2017-and-null-conditional-operators.489176/