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

Removed obsolete IOException #1668

Merged
merged 1 commit into from
Oct 3, 2024

Conversation

rPraml
Copy link
Contributor

@rPraml rPraml commented Oct 2, 2024

This PR removes a never thrown IO-Exception

@@ -2513,8 +2501,7 @@ private ScriptNode parse(
int lineno,
CompilerEnvirons compilerEnv,
ErrorReporter compilationErrorReporter,
boolean returnFunction)
throws IOException {
boolean returnFunction) {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I assume, that in former time a Reader was passed instead of String sourceString and that's why the IOException was still there. It can be removed and in all depending calls also.

Note: This might be a breaking change, if someone has implemented his own context with overwritten compileImpl

@rbri
Copy link
Collaborator

rbri commented Oct 2, 2024

fine for me i do not need backward compatibility here

@gbrail
Copy link
Collaborator

gbrail commented Oct 3, 2024

This is the kind of incompatibility I can live with. Thanks!

@gbrail gbrail merged commit 3d7b17b into mozilla:master Oct 3, 2024
1 check passed
@p-bakker p-bakker added the Potentially Breaking Change Issues that could break backwards compatibility label Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Potentially Breaking Change Issues that could break backwards compatibility
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants