Chance

roaring bitmaps may also help. But that may not be an option for all client languages.

> The changes to claim verification are interesting, but I am not sure if we should de-couple them from the error handling. I would propose first designing an appropriate API...

So since validation errors are fairly isolated, you may not need it. You could do something like: ```go type ValidationError struct { // maybe include a RWMutex? I don't know...

Edited my reply above.

If you guys are okay with the approach above, I'll implement them in the pull request. I understand the desire not to have external dependencies and since validation errors are...

The issue is here: https://github.com/santhosh-tekuri/jsonschema/blob/e29878922e1181aac622c253c9caa1f1baa7a612/schema.go#L241-L245 The second return of `Rat.SetString` is a `bool` which indicates whether or not it was successful. If unsuccessful, `num` is `nil`.

[These docs?](https://pkg.go.dev/encoding/json#Number) It doesn't mention that it must be a valid number. In fact, the accessor / parser methods return an error (as they are just using strconv under the...

Understood and I recognize that in a normal decoding flow, it would be caught with the `isValidNumber` function in the json package. However, I'm not unmarshaling the data first. There's...

Arg. I must have been thinking of a different json schema library which operates on `[]byte` or perhaps I'm just incredibly tired (its rather late/early here). Sorry about that! 🤦‍♂️

It seems openssl can be built with bazel using `rule_foreign_cc` https://github.com/bazelbuild/rules_foreign_cc/issues/337 I'm not familiar with bazel or c++ but I cruised down that rabbit hole.