We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If it is after merging #116, there is no performance difference between Parse and ParseStrict.
Parse
ParseStrict
goos: darwin goarch: arm64 pkg: github.com/oklog/ulid/v2 │ .old.txt │ .new.txt │ │ sec/op │ sec/op vs base │ Parse-10 9.158n ± 1% 6.051n ± 1% -33.92% (p=0.000 n=10) ParseStrict-10 14.515n ± 1% 6.106n ± 1% -57.94% (p=0.000 n=10) MustParse-10 10.095n ± 0% 7.076n ± 0% -29.91% (p=0.000 n=10) geomean 11.03n 6.394n -42.03%
The reason for having Parse and ParseStrict separately disappears. Perhaps it would be acceptable to perform strict checks in Parse as well?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
If it is after merging #116, there is no performance difference between
Parse
andParseStrict
.The reason for having
Parse
andParseStrict
separately disappears. Perhaps it would be acceptable to perform strict checks in Parse as well?The text was updated successfully, but these errors were encountered: