-
Notifications
You must be signed in to change notification settings - Fork 375
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
[RefC] Suppress arglist wrapper #3177
[RefC] Suppress arglist wrapper #3177
Conversation
… humanity and make them slaves. Under 2024, a only leaved job for every humans is adjusting spaces of source code, or just type gg0vG$== in vim.
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.
If I understand correctly, this inlines the notion of ArgList
into Closure
s. For the most part, this seems reasonable, except for the limit on the number of arguments.
A constructor for a particularly complicated data-type could easily overcome any finite limit on the number of arguments.
… avoid limits on the number of arguments and to reduce stack usage.
The previous commit changed the large argument list to be passed as an array. This may be overkill, but I think it avoids the limitation on the number of arguments. |
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.
Finished my read-through; with that, and prior feedback and requests addressed, I approve!
Description
Should this change go in the CHANGELOG?
implementation, I have updated
CHANGELOG.md
(and potentially alsoCONTRIBUTORS.md
).