so it gets wrapped in delay
I forget which way is which
thanks
Have a look at
Resource.make, it'll help you wrap things with a lifecycle
you can connect with jvisualvm
should tell you
Guys, is there example how to work with cancelable IO other than one in documentation? I cannot decipher it unfortunately. Here is what I want to achieve. I run synchronous DB query inside IO. I want to let user of this IO cancel query on timeout. For that I need to call java.sql.Statement.cancel() on statement that is used inside IO. How can I do that ?
I looked at IO.runCancelable and simply cannot understand how to use given SyncIO[CancelToken[IO]] and how to link it with suspended action of parent IO. Please advise.
it's much simpler to use bracket semantics
well
if you go down that road you end up implementing doobie anyway..
aside..
@rus right but you'd be better to add it than to start from scratch. You can use doobie's low-level api which just wraps jdbc one for one in
IO
and reading the implementation, I wonder if the difference is in the
future.value call that cats makes
monix just uses
future.onComplete
whereas cats checks preemptively if the future you gave it is already done
I haven't proved that it's from the
fromFuture change, I'm just trying to rule out suspects
only way you’ll know for sure.
that will just prove that in my benchmark scenario one is faster
it doesn't prove that my benchmark code matches the real use
might have misworded the name, tab complete it
without looking at it directly, I can't say whether or not it might be possible to be more aggressive about cancelation than what doobie is right now
but I would guess that a lot of this is just limitations in the underlying API
like how it's not actually async