Skip to content

Force the initialization of throwMethod in Definitions #1060

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
Feb 5, 2016

Conversation

VladimirNik
Copy link
Contributor

This change will fix the problem with unpickling of throw expression from TASTY representation.

@DarkDimius
Copy link
Contributor

LGTM after tests pass

@VladimirNik
Copy link
Contributor Author

Review by @odersky , @DarkDimius

@VladimirNik
Copy link
Contributor Author

/rebuild

1 similar comment
@VladimirNik
Copy link
Contributor Author

/rebuild

/** Lists core methods that don't have underlying bytecode, but are synthesized on-the-fly in every reflection universe */
lazy val syntheticCoreMethods = AnyMethods ++ ObjectMethods ++ List(String_+)
/** Lists core methods that don't have underlying bytecode, but are synthesized on-the-fly in every reflection universe */
lazy val syntheticCoreMethods = AnyMethods ++ ObjectMethods ++ List(String_+, throwMethod)
Copy link
Contributor

Choose a reason for hiding this comment

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

indentation here was intentional: member definitions are indented with 2 more spaces compared to class definitions.

odersky added a commit that referenced this pull request Feb 5, 2016
Force the initialization of throwMethod in Definitions
@odersky odersky merged commit 2c08c72 into scala:master Feb 5, 2016
@allanrenucci allanrenucci deleted the throwMethodInit branch December 14, 2017 19:25
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.

4 participants