Tim

I ended up creating the `emulators` package to replace `screenshots`: https://pub.dev/packages/emulators Will put it here as someone might find it useful :)

Added some changes to improve the API surface. * Added `response` to the `Env` struct. Defaults to `:default`, but also has a `:stream` option * Added `__pid__` to `Env`, for...

Maybe leaving this as an adapter option is better, as it will not be implemented for every adapter.

Been using `dartz` and also `fpdart` for a while now, thanks for the work guys! One thing that has always bugged me a little, is that the functions are all...

Used this in a few projects and I'm really liking this pattern. I found that it pushes me towards composability - creating small re-usable functions.

I needed a solution for a generic riverpod persistence layer, and ended up with this: https://github.com/tim-smart/riverpod_persistence/blob/main/test/riverpod_persistence_test.dart Would be nice to have something official!

I have been working on a alternative to `Stream` that is more functional in nature: https://pub.dev/packages/offset_iterator I have recently added `OffsetIterable.fromStreamEither` which might be of interest! You can see it...

Just in case someone stumbles upon this, here is something I'm using based around the example above. It is using `Option` from the dartz package, so you might want to...

Been playing with a do notation implementation using async / await functions. Reasonably simple, but it does have some trade-offs: ```dart typedef TaskEither = Future Function(); typedef _DoAdapter = Future...

The biggest downside is forgetting to use await when running a task only for its side effects (ignoring the result). It is easy to spot when actually using the return...