Explicit init of Thread and Fiber class variables #15369
Merged
+88
−22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds
Thread.init
,Fiber.init
that explicitly initialize the class variables defined onThread
andFiber
.In order to implement #14905 we'll need the ability to access
Fiber.current
which depends onThread.current
but if these accessors use the class getter/property macros then we'll enter an infinite recursion.AddsCrystal.once_init
to allow to remove theCrystal.once_mutex=
setter. It also removes the need for the__crystal_once_init
fun which won't be defined anymore —it's only kept for the legacy implementation.Those initializers are now explicitly called from a new
Crystal.init_runtime
method called byCrystal.main
, but also by the interpreter that doesn't callCrystal.main
—not currently needed, but it will be to reuse crystal/once to implement #14905.