Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[SE-0253] Introduce callables. #24299
[SE-0253] Introduce callables. #24299
Changes from all commits
932f108
4cce21f
d4737db
518bda2
9695a26
c744806
e213836
35607ed
8dcd1c6
4cb7ebf
cebbd63
0733cc0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I'm not sure that usages of
memberLoc
orlocator
are correct/ideal here.@xedin: could you please check these
ConstraintLocator *
usages?You suggested adding an "implicit call" path element, but I'm not sure where to use it - please advise!
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.
I think for
addValueMemberConstraint
it makes more sense to usememberLoc
rather thanlocator
, and forApplicableFunction
indeedlocator
is best.Regarding
implicit call
you don't have to worry about it right now, we can do it in the follow-up instead. I was thinking that it would be great to associate such new element with locator which belongs toApplicableFunction
something like<call anchor> -> implicit call -> apply function
so when argument conversions are expanded bymatchCallArguments
they'd get<call anchor> -> implicit call -> apply arg-to-param -> comparing #N to #M
locators.