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

Keep exception cause in some mtags exceptions #5205

Merged

Conversation

alexarchambault
Copy link
Contributor

Passing the cause exception to the Exception contructor makes it easier for users to know what's going on: the JVM or the printStackTrace method will print the current exception and its cause (and the cause's cause, etc.). That way, we know in more detail what the underlying cause of the exception is.

Passing the cause exception to the Exception contructor makes it easier
for users to know what's going on: the JVM or the printStackTrace method
will print the current exception and its cause (and the cause's cause, etc.).
That way, we know in more detail what the underlying cause of the exception
is.
Copy link
Contributor

@tgodzik tgodzik left a comment

Choose a reason for hiding this comment

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

LGTM!

@alexarchambault alexarchambault merged commit 09988e8 into scalameta:main May 5, 2023
22 checks passed
@alexarchambault alexarchambault deleted the keep-exception-cause branch May 5, 2023 12:57
jkciesluk pushed a commit to jkciesluk/metals that referenced this pull request May 19, 2023
Passing the cause exception to the Exception contructor makes it easier
for users to know what's going on: the JVM or the printStackTrace method
will print the current exception and its cause (and the cause's cause, etc.).
That way, we know in more detail what the underlying cause of the exception
is.
jkciesluk pushed a commit to jkciesluk/metals that referenced this pull request May 19, 2023
Passing the cause exception to the Exception contructor makes it easier
for users to know what's going on: the JVM or the printStackTrace method
will print the current exception and its cause (and the cause's cause, etc.).
That way, we know in more detail what the underlying cause of the exception
is.
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.

None yet

2 participants