Skip to content
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

Support of natural vararg #4

Open
mathze opened this issue Apr 13, 2021 · 0 comments
Open

Support of natural vararg #4

mathze opened this issue Apr 13, 2021 · 0 comments
Labels
backlog enhancement New feature or request

Comments

@mathze
Copy link
Contributor

mathze commented Apr 13, 2021

As found out in #1 the straight forward way of vararg support didn't worked and a 'workaround' was implemented.
This task is for further investigation on that field and hopefully find a way to make it work.
Motivation:
It is more natural to use fun aFunction(vararg values: String) instead of fun aFunction(@KwdArg(kind=ParameterKind.VARARG) values: List<String>?).
Beside the aesthetic aspect the former is less error prone, much shorter and better readable.

@mathze mathze added the enhancement New feature or request label Apr 13, 2021
@mathze mathze self-assigned this Apr 13, 2021
@mathze mathze added the backlog label Apr 13, 2021
@mathze mathze removed their assignment May 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant