-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Some runtime reflection calls use the wrong world age for their queries. #53105
Comments
I will leave it up to @aviatesk to say whether these are supposed to query the tls world or the max world. I think his intent was to query in the max world, independent of what worker task might be doing the query in some fixed world. |
Indeed. Functions like |
I think this is also an API decision. Right now folks use So we should steer them towards a public API like Note that #53088 exposes for the first time |
I tried to use
Typically, I would require the user to provide a
Is it the intention of |
Base.return_types, Base.infer_return_type and friends use
get_world_counter()
to query the world, this means that they will reflect on worlds further in the future than what they are actually executing.Maybe they should use
ccall(:jl_get_tls_world_age, UInt, ())
instead.The text was updated successfully, but these errors were encountered: