-
-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
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
Getting element access to break more consistent in long invocation chains. #967
Conversation
This had a number of side effects I need to review. At first glance some of these changes are for the better, but some we maybe don't want. |
This morphed a bit, and turned into getting properties to break more consistently with invocations and array access. |
So uh... is this ready for review now? Edit: I know I'm procrastinating on #923 , but I promise I'll get to it soon™ 😉 |
Whoops, yeah!
What I meant by this wasn't really clear after I reread it. I meant that this PR takes care of parts of #451, but not enough that #451 can be closed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
I really like how this makes it much less likely for array indexers to break.
|
||
// TODO too hard to change this for now, will do it in https://github.com/belav/csharpier/issues/451 | ||
var someVariable = this.Property.CallMethod( | ||
someValue => someValue.SomeProperty == someOtherValue___________________________ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also this isn't all that bad.
closes #956