You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both the :plugin and :runtime modules have many APIs that were accidentally introduced with a public visibility modifier. These APIs are currently annotated with @KotlinxBenchmarkPluginInternalApi and @KotlinxBenchmarkRuntimeInternalApi in the plugin and runtime, respectively.
The annotations require opt-in with a WARNING level. This level should be advanced to ERROR in a future release, and eventually, the annotated APIs should become internal, ceasing to be part of the library's public API.
Once the APIs are made internal, make sure to drop those that are not used internally.
The text was updated successfully, but these errors were encountered:
Are you sure the double step is necessary? Given the alpha status I'd not even bother with deprecations and make them internal now. I don't think there are many people using those APIs anyway.
I also believe that not many people use those APIs, if at all. However, I would like to make the migration smoother just in case. The deprecation cycle will be short, unlike in stable libraries.
Both the
:plugin
and:runtime
modules have many APIs that were accidentally introduced with apublic
visibility modifier. These APIs are currently annotated with@KotlinxBenchmarkPluginInternalApi
and@KotlinxBenchmarkRuntimeInternalApi
in the plugin and runtime, respectively.The annotations require opt-in with a WARNING level. This level should be advanced to ERROR in a future release, and eventually, the annotated APIs should become
internal
, ceasing to be part of the library's public API.Once the APIs are made internal, make sure to drop those that are not used internally.
The text was updated successfully, but these errors were encountered: