This seems to yield an undesirable

Arb

. I added the output from

values(RandomSource.Default).take(100)

. Am I composing

Arb

in an incorrect way?

So what's happening here is since arbs are infinite, the inner most one is never runs out of elements to move onto the next value of the outer loop.

Hmm. I ported this from a ScalaTest snippet.

Probably what you want is Arb.triple in kotest, although you can't have each arb depend on the previous one that way.

No, that also doesn’t work because I need to depend on the values.

I guess the problem is analogous to listOf(1,2,3).flatMap { generateSequence { 1 } }

I wrote it as a custom

Arb

now, but it felt quite low level to achieve what I needed.

Yeah this should be supported out of the box

I’ll share it publicly online I’ve written a quite extensive suite already with

4.0.5

how you finding the new property test stuff overall ?

I’m loving the new

checkAll

support

🙂

I’m written a bunch of

Arb

which can probably use some improvement but we might be able to move to

kotest

if you’re interested.

I thought having this Arb / Exhaustive thing was a brain wave of mine. Either that or unneeded complexity for no gain 😂

I’ve been using only

Arb

so far, but I could see where I could probably reduce stress on my test suites in quite some places by refactoring to

Exhaustive

I love the neatness of these tests

"cancelableF works for immediate values" {
    checkAll(Arb.result(<http://Arb.int|Arb.int>())) { res ->
      Either.catch {
        cancellableF<Int> { cb ->
          cb(res)
          CancelToken.unit
        }
      } shouldBe res.toEither()
    }
  }

Yes, the test look amazing to what they looked like in Arrow Fx with

IO

😅

lol

I finally managed to crack lowering

IO

into

suspend

and the result is quite nice

that's great. I've been doing some scala again recently, and having to pollute my signatures with an effect type is really ugly

Yes, that is completely gone now with the exact same semantics

You're just hooking into the continuation apparatus then, like sequence {} does

No, it also adds cancellation support and everything you’d find in an

IO

impl

oh right, wow

It’s a complete rewrite of Arrow Fx in

suspend

will this will become the default impl

And there is a lot more cool similar stuff in the works coming up soon 😉

Awesome! 👍

Thanks for using it 🙂