-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[CodeComplete] Markup default arguments #40351
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
Conversation
@swift-ci please test |
6bbf33e
to
fae72ab
Compare
@swift-ci please test |
Windows failure is known (and that test since disabled). |
fae72ab
to
5f701c2
Compare
@swift-ci please test |
Build failed |
@swift-ci please test macOS platform |
Build failed |
@swift-ci please clean test macOS platform |
@swift-ci please test |
5f701c2
to
2ca304e
Compare
Build failed |
@swift-ci please clean test macOS platform |
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! Thank you!
Build failed |
Add `<callarg.default />` nodes to the annotated description of a completion result for all arguments that have defaults. Resolves rdar://85904660.
Now that arguments are marked up with whether they have a default or not, clients may not need the extra call (that has no default arguments). Add an option to allow not adding this item. Resolves rdar://85526214.
2ca304e
to
65ef802
Compare
@swift-ci please smoke test |
Add
<callarg.default />
nodes to the annotated description of acompletion result for all arguments that have defaults.
Also add a new option to control whether or not an extra item is added
for calls with no default arguments or not (since clients can now use
the marked up argument to check this themselves).