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

do not set eval-type NONE value in a thread-local #4530

merged 3 commits into from Mar 18, 2017


Copy link

@kares kares commented Mar 14, 2017

resolves #4529

a follow-up on #4215 + a FIXME fixed that I've bumped into way too often :)

... any chance to get this in for - getting a lot of log on TC // cc @headius @enebo

@kares kares changed the title do not set eval-type NONE in a thread-local do not set eval-type NONE value in a thread-local Mar 14, 2017
Copy link

enebo commented Mar 14, 2017

@kares It seems ok to me but fix your bracing to match our style } else {

@kares kares force-pushed the test-null-eval-type-dejavu branch from 328b3d0 to 91926ef Compare March 14, 2017 14:41
Copy link
Member Author

kares commented Mar 14, 2017

@enebo done and thanks. there's an additonal commit: 91926ef ... figured that the BlockBody might not report the correct (previously set) eval-type when there's a jitted body (can remove if there's reason for that).

@kares kares added this to the JRuby milestone Mar 14, 2017
@kares kares merged commit df15739 into master Mar 18, 2017
@kares kares deleted the test-null-eval-type-dejavu branch March 18, 2017 10:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

plenty of [org.jruby.EvalType] (value [NONE]) in thread-locals
2 participants