Alex Kocharin

This is not just a performance issue, this is algorithmic complexity issue. ```md [ref1]: url 'title' [ref2]: url [ref3]: url [ref4]: url ... [ref10000]: url ``` Where does first reference...

`npm i -g --prefix xxx serve` will install stuff to different folders. I'm taking `serve` as an example here because it has less dependencies: On linux (npm 8.8.0): ``` xxx/bin...

> It would be nice to upstream this in some manner I agree. Can you send a pull request? PS: `store_labels` is probably not necessary, instead can just always store...

Yeah, I had my doubts about this one as well for some time. ### Why? Not clear what the behavior should be if code rule is disabled. I wrote `markdown-it`...

> I like the idea, however, how could this work, given that individual rules don't have any "initialisation hook" themselves? In theory, every markdown-it rule can be wrapped in its...

> Yeh ughh, I'd be very wary of doing this as obviously any divergences make it more difficult to port fixes/improvements you make here and ensure markdown-it-py is kept in-sync...

> so I would rather also invest my time there and seeing what I can do with Not a discussion for this repo, but... "Parser plugins cannot currently be written...

Please send a pull request for this library. We might get this change in (if performance impact is negligible).

my guess: code coverage + think really hard

First you detect the collision using onCollision hook (don't forget scene filters). Then you get actor pointer from collision callback, verify that it's valid (flags), and remove it (scene.removeActor is...