Closed evant closed 9 months ago
The implementation is
fun <T> Assert<T>.isSameAs(expected: T) = isSameInstanceAs(expected)
so I don't think it's that important
The implementation is
fun <T> Assert<T>.isSameAs(expected: T) = isSameInstanceAs(expected)
so I don't think it's that important
I thought in the past you wanted me to keep tests for the old APIs, but it's absolutely possible I'm confusing this with other projects. I, too, think it's reasonable to omit.
The implementation is
fun <T> Assert<T>.isSameAs(expected: T) = isSameInstanceAs(expected)
so I don't think it's that important
I thought in the past you wanted me to keep tests for the old APIs, but it's absolutely possible I'm confusing this with other projects. I, too, think it's reasonable to omit.
Depends on what it was testing, anything more complicated than forwarding to a function which already has a test I would say to keep, yeah
This makes it more clear these functions are about instance identity see: https://truth.dev/comparison
495