Cats has chosen to require this method of all monad implementations as opposed to just a subset
So this problem would really need to be solved to be consider an acceptable Monad
But I also came across: reactor/reactor-core#2147
suggesting that stack-safe flatMap is simply not going to be possible for the foreseeable future
So it's probably safe to assume that Monad cannot be a part of this extensions layer
That said, it looks like you're only interiting Monad due to the use of 'Bracket'
so if you're willing to give up Bracket, then a subset of these other operations should still be doable
so if you're willing to give up Bracket, then a subset of these other operations should still be doable
Partly yes, this is when I encounter problem that when I use resources that needs to be closed depending on the outcome, it’s not easy to write the code. And I found this bracket code and found it easy to use it. So I apply it here.
What do you think? And where would we put it?
Perhaps something like this?
package reactor.util.scala.context
import reactor.util.context.Context
object SContext {
implicit class ContextOps(context: Context) {
def getOrNone[T](key: AnyRef): Option[T] = {
val x = context.getOrEmpty[T](key)
if(x.isPresent) Option(x.get())
else None
}
}
}
how about putting on the context package object?
2 replies
Side thought: the original
but in Scala we have the opportunity to use a
getOrEmpty type param is just for convenience and can't actually perform a type check(throwing a ClassCastException if it's not of type T),but in Scala we have the opportunity to use a
TypeTag and return None in the case that there is a value for the key, but of the wrong type.
2 replies
I’ve raised #72 to removes deprecated caused by using Scala 2.13, such as using
Stream instead of LazyList. Some will cause breaking changes (especially when returning Stream, it is now returning LazyList). But those with parameterStream, I made it deprecated and provide another operator using LazyList.
Please have a look and see if it makes sense