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
The testkit inherently DOES pry into a lot of the actor runtime internals of the cluster. It provides mocks and test probes and various things that pretend to be behavior actors but are not.
This needs to use internal APIs, and we do so by using a @testable import in the TestKit.
Making it not need that is a painful task making a lot of "old runtime" types public, which we absolutely don't want to do, given that now actors and distributed actors are in the language, so we would not want to expose MORE of our previous infrastructure.
The testkit inherently DOES pry into a lot of the actor runtime internals of the cluster. It provides mocks and test probes and various things that pretend to be behavior actors but are not.
This needs to use
internal
APIs, and we do so by using a @testable import in the TestKit.Making it not need that is a painful task making a lot of "old runtime" types public, which we absolutely don't want to do, given that now actors and distributed actors are in the language, so we would not want to expose MORE of our previous infrastructure.
If we had the
package
access visibility this would solve the issue. https://forums.swift.org/t/se-0386-package-access-modifier/62808/This prevents the source-compatibility-suite to build the cluster in release mode.
The text was updated successfully, but these errors were encountered: