Skip to content

Commit cb065da

Browse files
djspiewakSethTisue
andauthored
Update 2025-08-17-custom-error-types.md
Co-authored-by: Seth Tisue <seth@tisue.net>
1 parent 3c9843b commit cb065da

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

collections/_posts/2025-08-17-custom-error-types.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -145,6 +145,6 @@ Rather than trying to impose a particular multi-channel composition semantic on
145145

146146
Hopefully you find this technique helpful! This has been in the works for a *surprisingly* long time (I think it was first suggested in the Typelevel Discord about two or three years ago), and it was Thanh Le ([@lenguyenthanh](https://github.com/lenguyenthanh)) who ultimately pushed it over the line. Huge shoutout!
147147

148-
Even more excitingly, this is a bit of taste of the next phase of the effect type ecosystem. Scala is continuing to move heavily in the direction of implicit capabilities for these types of behaviors, and while efforts such as Caprese are still a long way from bearing real-world fruit, much of the work that is being done in that direction also creates the primitives needed to encode a compositional capabilities ecosystem for our existing production effect types, such as Cats Effect `IO`!
148+
Even more excitingly, this is a bit of a taste of the next phase of the effect type ecosystem. Scala is continuing to move heavily in the direction of implicit capabilities for these types of behaviors, and while efforts such as Caprese are still a long way from bearing real-world fruit, much of the work that is being done in that direction also creates the primitives needed to encode a compositional capabilities ecosystem for our existing production effect types, such as Cats Effect `IO`!
149149

150150
Cats MTL will continue to evolve in this area, with an eye towards advancing the capabilities and improving syntax and ergonomics of this type of functionality both now and in the future.

0 commit comments

Comments
 (0)