Move process parse exceptions to sys.error instead of a custom exception - #25675
Merged
Conversation
Contributor
|
Too late to object, but
implies it may be useful internally. Also, even if it's not intended for external consumption, seeing its name in a stack trace is useful. I thought |
alexarchambault
pushed a commit
to plasmon-scala/scala3
that referenced
this pull request
Jun 16, 2026
âĶion (scala#25675) Having a custom private exception, that thus can't be caught externally aside from RuntimeException anyway, is weird. ## How much have you relied on LLM-based tools in this contribution? not ## How was the solution tested? new tests [Cherry-picked 2f82225]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Having a custom private exception, that thus can't be caught externally aside from RuntimeException anyway, is weird.
How much have you relied on LLM-based tools in this contribution?
not
How was the solution tested?
new tests