Owen Shepherd
Owen Shepherd
Exposing the data as JSON is a good idea for performance reasons, as parsing JSON is faster than parsing JS. See https://github.com/GoogleChromeLabs/json-parse-benchmark
@ktrz this should be good to review now
@jeertmans That API looks really nice! I'd love to see this in `logos`.
Yes, that's sort of what I expected. I'll probably switch to `logos` for my particular lexer, just because I really don't want to compile regex during runtime at all, not...
You can use the logos crate as an external lexer with lalrpop, so I don't doubt lalrpop could switch to using/reexporting logos if there was a push to do so.
I want to highlight a couple of quirks/features of the JSON schema spec, starting from the fact that JSON schema keywords add constraints, so it's possible to write a schema...
Ah, well I'm okay, I've solved a few ambiguities without much trouble. I just think this error message needs to be updated to point to a resource that helps solve...
Well at the very least we can stop telling people to look through the manual for information that isn't there.
@ktrz this should be ready for another pair of eyes
@fmease yeah trust me I didn't want to use them. I don't suppose there's another way to have the overlapping instances of `ExactSizeIterator` accepted by the compiler? I need this...