István Pásztor

It would become significantly slower with `codePointAt` while in it's current form (with `charCodeAt`) it'll work in most cases but can report false positives when the text contains UTF-16 surrogate...

I happen to use the exact same version (and used this version to compile the extension). And "it works on my machine" :-D However, I might have made a mistake....

I've found some issues that caused problems on my machine only under certain conditions. Uploaded a new version (v2.1.11). You can give it a try.

Sorry but I'm not using Sphinx so I have no idea what's wrong.

I don't agree with some of the design decisions of the standard flags but that is still the standard (and builtin) so people should consider using it when it covers...

`Flag` vs `IntFlag`: overcomplicated - it's enough to have an integer flag with the ability to auto-assign flag member values. > One subtle thing I discovered about Flag vs. working...

Thanks for the PR. It looks good but one of the unit tests hangs up - that should be at the very least skipped. This is one of those old...

Thanks for letting me know. To be honest I was thinking about adding write functionality at the time of implementing the library but that would have introduced a few problems...

> However, i've made changes to json-cfg nodes so that they auto create objects and populate them with the default values when they are missing. This is a strategy that...

1. I would add file write support to the library only after a proper write implementation (that retains comments, some of the formatting e.g..: wrapped/unwrapped lists/objects). 2. I wouldn't add...