We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
null == value
I have defined several extension methods (which are implicitly imported):
def boolean operator_equals(AtomicLong left, int right) {} def boolean operator_equals(AtomicLong left, short right) {} def boolean operator_equals(AtomicLong left, long right) {} def boolean operator_equals(AtomicLong left, float right) {} def boolean operator_equals(AtomicLong left, double right) {} def boolean operator_equals(AtomicLong left, byte right) {} def boolean operator_equals(AtomicLong left, Number right) {} def boolean operator_equals(AtomicInteger left, int right) {} def boolean operator_equals(AtomicInteger left, short right) {} def boolean operator_equals(AtomicInteger left, long right) {} def boolean operator_equals(AtomicInteger left, float right) {} def boolean operator_equals(AtomicInteger left, double right) {} def boolean operator_equals(AtomicInteger left, byte right) {} def boolean operator_equals(AtomicInteger left, Number right) {}
The following lines are compiled without error:
def void fct(AtomicInteger value) { if (value == null) { } }
But, the following lines cause a compilation error (ambiguous feature call):
def void fct(AtomicInteger value) { if (null == value) { } }
As you could see, the operands of the == operator are switched. Semantically, both definitions are equivalent. Both should compile without error.
==
The text was updated successfully, but these errors were encountered:
This issue should be fixed within Xbase. See Issue 300 for Xbase.
Sorry, something went wrong.
No branches or pull requests
I have defined several extension methods (which are implicitly imported):
The following lines are compiled without error:
But, the following lines cause a compilation error (ambiguous feature call):
As you could see, the operands of the
==
operator are switched.Semantically, both definitions are equivalent.
Both should compile without error.
The text was updated successfully, but these errors were encountered: