Kat Marchán
Kat Marchán
I’ll take a PR for this as long as it’s a default feature
huh. ....I guess whoever copy-pasted that number failed to copy paste the final `1` (probably me)? Sorry about that. Would you like to PR this change?
I'm pretty sure this is an oversight, but it's been a while. It seems pretty reasonable to me to expect either Failure or Success to always run at least once....
https://github.com/tree-sitter/tree-sitter-javascript/issues/163 suggests that the javascript tree sitter syntax already supports this? somehow? as long as you have html installed?
While `Thinker`s &co are fundamentally stateless, the really good reason for having serializable builders is so you can build up your AI logic using external tools/node-based graphical builders, or even...
This can definitely happen in any kind of environment with high writes. I'm assuming you're properly awaiting/calling `.close()` on your Writers. It might also have to do with mmap, so...
I would not expect that either, that's very strange--considering there's separate files and filenames for everything. The only way I can see this happening is if you're trying to write...
@bryanlarsen I wouldn't do that: cacache takes care of doing things as atomically as possible, which is how it can operate completely lockless. Having this kind of two-step operation might...
because if something happens after the `exists()` that corrupts or removes the package, you then fail to rewrite the package
this sounds nice. I'd take a PR for this as long as it's not semver-breaking.