add ManagedRuntime module, to make incremental adoption easier

[tim-smart]

No description provided.

[changeset-bot]

🦋 Changeset detected

Latest commit: 6e87576

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 15 packages

Name	Type
effect	Patch
@effect/cli	Patch
@effect/experimental	Patch
@effect/opentelemetry	Patch
@effect/platform-browser	Patch
@effect/platform-bun	Patch
@effect/platform-node-shared	Patch
@effect/platform-node	Patch
@effect/platform	Patch
@effect/printer-ansi	Patch
@effect/printer	Patch
@effect/rpc-http	Patch
@effect/rpc	Patch
@effect/schema	Patch
@effect/typeclass	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[mikearnaldi]

not sure if this helps adoption or just induces users into a bad pattern, namely using using would lead to scope being open and closed on demand instead of having the layer survive for the program lifetime

[tim-smart]

not sure if this helps adoption or just induces users into a bad pattern, namely using using would lead to scope being open and closed on demand instead of having the layer survive for the program lifetime

Having it implement Disposable is definitely up for debate. The main thing I wanted to tackle was providing a way to run effects in non-effect land in a nice way without having to juggle a Scope, Runtime and also memoizing the runtime.