One thing I miss about the now-deprecated `shouldBeInstanceOf` that took a block was that I ended up...

# kotest

[bbaldino]

One thing I miss about the now-deprecated shouldBeInstanceOf that took a block was that I ended up doing things like this:

someList.first().shouldBeInstanceOf<Foo> {
  // 'it' is cast to 'Foo'
  it.someMethodOnFoo() shouldBe ...
}

whereas now I end up doing something like

with (someList.first()) {
    shouldBeInstanceOf<Foo>()
    someMethodOnFoo() shouldBe ...
}

and I prefer the first style, but perhaps just a personal preference.

[sam]

shouldBeInstanceOf

should smart cast

[bbaldino]

I don't think contracts are smart enough to smart cast an element from a list though

[sam]

you could do .apply{} on it maybe

[bbaldino]

Yeah I thought about that but it's not too different from the with.

[Javier]

and shouldBeTypeOf() doesn't smart cast too?

[bbaldino]

Which, of course, isn't a huge difference from the new style, but, I still think I like the old way.