You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Through some historical problems, I know that the overloading operators which used by wurst are ambiguous
but support overloading the not-used operators by user maybe a good idea
just like
{ } :: # $ ^ & ~ | !
if it support we can use by myself definition like "&" as "and" , "!" as "not "
The text was updated successfully, but these errors were encountered:
There is an open ticket with the exact same name, you can comment/react there. #297
Please verify that an issue doesn't already exist and that it's a valid ticket before creating it 👎
Also, adding overloading for such operators { } ^ & ~ that don't even exist in the language, doesn't really make sense imo.
In the end you have to remember that all of this is syntactic sugar. Simply using functions is more intuitive and readable in most cases. Even in languages where such overloading exists, it is rarely used in production. Overloading for certain packages, like vectors, can make sense. Redefining "and" as & not so much.
Through some historical problems, I know that the overloading operators which used by wurst are ambiguous
but support overloading the not-used operators by user maybe a good idea
just like
{ } :: # $ ^ & ~ | !
if it support we can use by myself definition like "&" as "and" , "!" as "not "
The text was updated successfully, but these errors were encountered: