Skip to content

processArgs is final for some tailrec #12589

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

Merged
merged 1 commit into from
May 26, 2021
Merged

Conversation

som-snytt
Copy link
Contributor

Fixes #12588

Copy link
Member

@smarter smarter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Otherwise LGTM

Long lists of compiler args are not unusual,
so avoid running out of stack.
Copy link
Member

@smarter smarter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice improvements, thanks! By the way, if you feel like doing more work on our settings infrastructure, I recently discovered that SettingsState#update would either mutate or not mutate the original SettingsState depending on whether a setitng value had been read from it previously or not. This is awful design and makes it impossible to rely on it (#11582 (comment)), so it'd be great if we could replace that by something less weird like simply using an immutable HashMap for settings (or port whatever Scala 2 uses nowadays).

@smarter smarter merged commit 74ea1af into scala:master May 26, 2021
@som-snytt som-snytt deleted the issue/12588 branch May 26, 2021 15:15
@Kordyjan Kordyjan added this to the 3.0.1 milestone Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Stack overflow when processing many command line arguments
3 participants