Tags: ansel1/vespucci

Update github actions

more benchmarks

Contains assertions should always fail if there is a match error

And print the details of the match error.

can't use retract yet. go < 1.16 barfs

faster empty check in contains

don't normalize in place in most cases

For most of the API service, it is safer to assume users don't want the original value modified, especially with Contains().  Caller should Normalize() first to save time if they expect to use the same value many times with this package.

Optimization for checking an empty time.Time

remove old 1.12 build, and add new badges

bug fixes to error messages

updated README