-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
add @callsuper macro #18252
Labels
design
Design of APIs or of the language itself
help wanted
Indicates that a maintainer wants help on an issue or pull request
speculative
Whether the change will be implemented is speculative
Comments
StefanKarpinski
added
speculative
Whether the change will be implemented is speculative
design
Design of APIs or of the language itself
labels
Aug 26, 2016
Closed
StefanKarpinski
added
the
help wanted
Indicates that a maintainer wants help on an issue or pull request
label
Aug 26, 2016
do the types used in invoke actually have to be supertypes of the values provided? |
Or maybe |
Closed
As a new feature, can be considered post-1.0. Triage also feels it's unlikely we'll remove |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
design
Design of APIs or of the language itself
help wanted
Indicates that a maintainer wants help on an issue or pull request
speculative
Whether the change will be implemented is speculative
As per #13123, we could add a
@supercall
macro that sweetens the interface toinvoke
and makes it more intuitive. My current implementation:Support for keyword arguments could be taken from #11165.
The text was updated successfully, but these errors were encountered: