Daniel Nephin

That's the big question for sure. My hope is that it can be backwards compatible for 1.18+. The function signatures have changed, but they aren't methods on a type. I...

The `options ...cmp.Options` parameter to `DeepEqual` isn't changing. I think those should be ok, unless I'm missing something.

Ahh, if I understand correctly you mean when the args passed to `DeepEqual` are different types, but a `Transformer` changes the type. That is possible. It seems strange that someone...

I'm still not sure if we need a v4 for this. I wrote up #257 with some other changes we might want to make for a v4 release. I think...

Thank you for the feedback! I like the idea of using color to improve the visibility of the failure messages. With type constraints I think we'll be able to remove...

I like it! Maybe something like `-update={ask,prompt,interactive}`. Use the same flag, the value is still optional.

I looked into this a bit, and it sounds like unfortunately it is not possible. See https://echorand.me/posts/go-test-stdin/. Go tests are run with `os.Stdin` set to /dev/null, so there's no input...

Hi @thaJeztah ! Thanks for raising this issue. The way I would generally check error types would be: ```go // using func(err) bool assert.Assert(t, IsNotFound(err), "err=%v", err // using errors.As...

Works for me. My primary reason for opening this issue is to document that we will likely be removing squash at some point. There was a request to add it...

It sounds like this is some misunderstanding in this thread so I will attempt to clarify. Multi stage builds should handle every use case of squash, as well as many...