A modern programming language that makes developers happier.

kotlinlang

Arrow 2.2.0 is out! <https://arrow-kt.io/community/blog/2025/11/01/arrow-2-2/>

&gt; Our advice is to fully migrate to the context-style API if possible
Do you mean even for production code? Does using context parameters currently have any known caveats for the Raise dsl usage? I haven't really yet adopted them, being a bit scared to bring in hard-to-find bugs into production code, or having less IDE support than needed.

Sorry, I think that sentence was not clear in the blog post. The recommendation is "use extension-style or use context-style, but not mix them"

Oh... so that's not a recommendation to use context parameters... I guess I should wait until they stabilize for production code, then. Thanks!

Cool, thanks for the next great version! I was really waiting for the DSL bridge functions for context parameters and I am happy to see some, if not all! Added a feature request for the missing ones, but I am not sure how to get "all" of them without missing some... :wink: (see <https://github.com/arrow-kt/arrow/issues/3777>)

thanks for taking the time! I've tried to port the entire API, but it proved out to be difficult because it's spread in different files. And indeed, I forgot some! :disappointed:

I would love to help and do a PR, Alejandro, I just was not sure about the style, so where to put all of the functions. There are even more to consider if you look at Resource scopes and such....

we're just migrating Raise for now; all functions should either go to RaiseAccumulate.kt if they have something to do with accumulation (so the ones you mention in your issue) or in Raise.kt otherwise