| Age | Commit message (Collapse) | Author |
|
reflect.DeepEqual fails when comparing reflect.Value containing float64. I
think it cannot make sense of reflect.Value pointer tricks and directly
compare reflect.Value.val fields which contain the float value in 64 bits,
but a pointer to the float in 32 bits.
Fortunately, interface{} which have a similar memory layout, compare correctly,
so we just turn the []reflect.Value into []interface{}.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This brings the test coverage back to 100%.
|
|
The function sort be sorting the uintptr itself, not the address of it.
Also, the previous code could easily panic on an unaddressable
reflect.Value since it was trying to take an address.
|
|
|
|
|
|
This commit moves the TestSortValues function from dump_test.go to
common_test.go to mirror the new implementation location. It also
slightly formats the tests to be consistent with the rest of the package.
|
|
This commit moves the new code related to sorting reflect.Value items into
common.go since it is accessed by both the formatter and the dumper. It
also adds comments to the new functions and unexports SortValues since it
should be an internal function only.
|
|
|
|
config: add SortKeys option to sort native map keys before display
|
|
The previous version of SortKeys was sorting only native types. Now, if
the type is unknown it defaults to its reflect.Value.String()
representation which at least guarantees display stability.
|
|
If ConfigState.SortKeys is true, then dump and format will sort map keys
before displaying them. Only native types (bool, ints, uint, uintptr,
string) are supported, other slices are left unchanged.
The motivation is to have more diffable output, mostly for test purpose.
|
|
This commit updates the test coverage report in include the latest
tests for the recent cgo handling updates for char, unsigned char,
and uint8_t arrays.
|
|
This commit adds a script which can be used to generate the test coverage
report. It detects whether or not gcc is installed and adds the necessary
build tag to enable the new cgo tests when gcc is available.
|
|
This commit adds tests for the recent cgo handling of char, unsigned char,
and uint8_t arrays.
In addition, it adds an architecture for the cgo specific testing based on
build constraints. This was done because spew itself does not require
cgo, but in order to test its handling of the cgo types it needs to be fed
cgo data. Rather than force all users to have a system which supports cgo
and an external compiler just to run the tests, the cgo test support must
explicitly be turned on via a build tag.
|
|
This commit adds support for dumping a few cgo types like hexdump -C as
requested in issue #11. In particular, it now handles char [#], unsigned
char [#], and uint8_t [#].
|
|
This commit updates the test coverage report in include the latest
tests for the nil slice change.
|
|
This commit adds tests for the nil slice change.
|
|
This commit modifies the code to detect nil slices and display them as
<nil> (as opposed to simply empty slices). For most instances a nil slice
can be treated the same as an empty slice, but there is a difference and
things like reflect.DeepEqual notice. This change makes it clear whether
the type in question is a nil slice or an empty slice.
|
|
This commit updates the test coverage report in include the latest tests
for the packed nil interface issue reported in issue #12.
|
|
This commit adds tests for nil interfaces packed inside maps and slices to
test the recently added fix for issue #12.
|
|
This was reported by shurcooL as issue #12.
|
|
|
|
|
|
|
|
This commit adds tests for the new Sdump function both at the package
level and as a part of a ConfigState.
|
|
This commit adds a function named Sdump which works exactly like Dump and
Fdump except it returns the formatted output as a string. This serves the
same purpose as the the Sprint* family of functions.
|
|
|
|
|
|
Include byte slice hexdump output in sample dump output.
|
|
This commit updates the test coverage report to include the latest
tests for the new byte array and slice hexdump -C behavior.
|
|
This commit adds tests for the new byte array and slice hexdump
functionality as specified in issue #9.
|
|
This commit modifies the Dump family functions to output byte arrays and
slices like hexdump -C as specified in issue #9.
|
|
This paves the way to improve how byte arrays are output as well as
increases the flexibily of the functions.
|
|
This commit updates the test coverage report to include the latest tests
for the new ContinueOnMethod option.
|
|
|
|
This commit expands on TShadwell's work attached to issue #8. It
rounds out the documentation for the new option.
|
|
|
|
after an error or Stringer interface is encountered.
|
|
|
|
This commit adds tests for the new Sprint, Sprintf, and Sprintln functions
at the package level and as part of a ConfigState.
|
|
This commit implements wrappers for the fmt.Sprint, fmt.Sprintf, and
fmt.Sprintln functions as requested in issue #7.
|
|
|
|
|