Files
tasks/common/effect/README.md
Stephan BehnkeandGitHub 72ac3fe957 Move packages from internal to common (#7526)
## What changed?
<!-- Describe what has changed in this PR -->

Moved all packages inside `/internal` to `/common`.

## Why?
<!-- Tell your future self why have you made these changes -->

While the `internal` package provides the benefit of preventing any
external party from depending on them, we find that in practice this has
little benefit.

Our compatibility guarantees do not coverage any APIs in `common`
anyway.

Furthermore, splitting commonly-used packages into two places hinders
discoverability. And adds (albeit minor) mental friction.

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->

Compiler.

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

External users could start relying on these packages. But that's their
risk assessment to make. There are no guarantees (just like for any
other package in this repo!) outside of the external APIs.

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
2025-03-25 21:12:46 +00:00

85 B