I reread carefully the messages and examples above and looks like I was wrong

Empty is concentrated on equals with len.
Zero is concentrated on equals with zero value objects.

And these are separate checkers, and zero should cover not only zeros, but the full list:

	zeros = []interface{}{
		false,
		byte(0),
		complex64(0),
		complex128(0),
		float32(0),
		float64(0),
		int(0),
		int8(0),
		int16(0),
		int32(0),
		int64(0),
		rune(0),
		uint(0),
		uint8(0),
		uint16(0),
		uint32(0),
		uint64(0),
		uintptr(0),
		"",
		[0]interface{}{},
		[]interface{}(nil),
		struct{ x int }{},
		(*interface{})(nil),
		(func())(nil),
		nil,
		interface{}(nil),
		map[interface{}]interface{}(nil),
		(chan interface{})(nil),
		(<-chan interface{})(nil),
		(chan<- interface{})(nil),
	}

If user uses assert.Equal(t, 0, len(warningMsg)) then we suggest assert.Empy(t, errors).
If uses uses assert.Equal(t, "", warningMsg) then we suggest assert.Zero(t, warningMsg).

Also need to grep some statistics and understand the history of creation of Zero.
To enable it by default or not? Really it useful or not?

zero: use zero instead of asserr.Equal(t, 0, v) #75

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

zero: use zero instead of `asserr.Equal(t, 0, v)` #75