(it doesn't seem like there's a memoize for `suspend fun`s...?)

The documentation specifies memoize should only be used for pure functions, which makes sense it seems. Suspend functions typically have side effects.

True, I noticed that... but when you have a call to another microservice and you don't want to make the call again with the same params... a memoized for a suspend fun would come in handy even if not pure... worst case would be to cache anything that has a Right, and retry Lefts...

Indeed, then we talk about caching rather than functional memoize

Yeah... but it seems like Arrow 2.0 is directed towards real use-cases rather than functional theory... so I wonder if that's so terrible? Especially with the fact that it seems like an Arrow standard is that whatever functions are marked with

suspend

aren't pure anyways... and that's what such a

memoized()

would do, return another impure

suspend fun

so we're not messing with any of the functional laws, just making convenience methods for similar use cases...