refactor: Fix placement of access of scala.scalanative.runtime definitions
#3805
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…llvm.dothing` instead of yielding thread
…ace of usage * Merge javalib Scala 2/3 enums implementations * Decouple scalanative_current_nanos used by GC from runtime * More strict access to scalanative.runtime types
…ds on Comperable: Java defined types are erased to Object, Scala defined ones are preserved in the generic type
…it, not an alias to java.lang.Clonable
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
scala.scalanative.runtimedefinitions used only by javalib to javalib projectscala.scalanative.runtimefrom javalibscala.scalanative.runtimetypesscala.scalanative.runtime.libc=>scala.scalanative.runtime.ffiscalanative_nano_timeused by javalib from their usage in Immix/Commix GC.