arrow-resource
Arrow Resource (Kotlin)
Quick start
- Use
resourceScope { ... }at lifecycle boundaries. - Define each resource with
resource { install(acquire) { a, exitCase -> release } }. - Compose with
.bind(); useparZipfor independent parallel acquisition. - Read
references/resource.mdfor patterns and concrete examples.
Workflow
- Identify the acquire step and the release step.
- Implement a
Resource<A>usinginstall. - Create reusable constructors on
ResourceScopewhen needed. - Compose resources into higher-level resources with
.bind(). - Execute in
resourceScopeand keep finalizers idempotent.
Usage guidance
- Prefer Resource over
use/try/finallywhen you need suspend finalizers or MPP support. - Use
ExitCaseto handle rollback/cleanup differences. - When mixing with typed errors, pick nesting order deliberately to control
ExitCaseseen by finalizers.
References
- Load
references/resource.mdfor API details and end-to-end examples.
More from alexandru/skills
cats-effect-io
Scala functional programming with Cats Effect IO and typeclasses. Use for wrapping side effects, modeling purity, choosing Sync/Async/Temporal/Concurrent, handling blocking I/O, and composing resources, fibers, and concurrency safely.
39cats-effect-resource
Scala resource lifecycle management with Cats Effect `Resource` and `IO`. Use when defining safe acquisition/release, composing resources (including parallel acquisition), or designing resource-safe APIs and cancellation behavior for files, streams, pools, clients, and background fibers.
36cats-mtl-typed-errors
Scala typed errors with Cats MTL Raise/Handle and allow/rescue. Use for designing custom domain error types without EitherT, while keeping Cats Effect and ecosystem composition. Covers Scala 2/3 syntax and IO-only or F[_] usage.
23akka-streams
Scala reactive streaming with Akka Streams and Pekko Streams. Use for dataflow and reactive programming patterns, testing stream components, and understanding when NOT to use streams (prefer plain functions for transformations and I/O).
20arrow-typed-errors
Kotlin + Arrow typed error handling using Raise DSL and wrapper types (Either/Option/Ior/Result/nullable), including validation with accumulation, interop with exceptions, and custom error wrappers. Use for designing or refactoring error modeling, converting exception-based flows, building smart constructors, accumulating validation errors, or integrating Outcome/Progress-style wrappers with Arrow.
16kotlin-java-library
Kotlin design for Java libraries and Java consumers. Use when building Kotlin code intended for Java callers, aligning with Java interop, JVM annotations, records, and backward/binary compatibility rules.
14