feat(core): hybrid Effect/Promise interface & no-await design #896
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.
This changes Resource to produce an interface that is compatible with both Effects and Promises.
This new approach encourages not calling
await
until the end (although there's nothing stopping you). You can alsoyield* Worker(..)
to use Alchemy natively in Effect.runtime
,infrastructure
orui
implementations of a resource (a better, effect-native approach to the previous runtime bootstrap that tried to do the same with esbuild).How to define a Resource natively in Effect:
How to use without
await
: