Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Crash when boolean attribute and method clash #1191
The following code results in a crash
The stack trace is
changed the title from
Crash when booleanattribute and method clash
Crash when boolean attribute and method clash
Jan 13, 2018
The line that breaks in this scenario is:
This case is trying to throw error code
However, if we reverse the order to
The order of compilation is reversed and no error is thrown at all. Both this case and the first case should throw a 1009 error, but neither does, each for different reasons.
PR #1007 for Issue #962 introduced the notion of having the generated API methods present in the model. There should be error 1009 reported when somebody writes code manually that clashes with generated API
So getIsAdmin() in this example results from that and message 1009 should be generated. PR #1007 hence has some bugs It also seems that the order (whether dup of generated method or the attribute come first) also makes a difference.