I appreciate that you first tried to optimize the original Python code. Idiomatic Python is unfortunately disappointingly slow and not so interesting to compare to.

It’s amazing how much Python punishes you for modularizing your code

I really enjoy making Python faster. I feel like the sweet spot for me is proving a concept with the dumbest possible implementation to show that something would work, and then using that as a comparison implementation to prove that later improvements match the results of the dumb, obviously correct implementation.

I wonder if these lints could have been expressed as semgrep rules?

Could this ast.sprint ast.walk optimization make libCST or bandit faster? 
<a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=39111747">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=39111747</a><p>libCST: <a href="https:&#x2F;&#x2F;github.com&#x2F;Instagram&#x2F;LibCST" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Instagram&#x2F;LibCST</a><p>bandit: <a href="https:&#x2F;&#x2F;github.com&#x2F;PyCQA&#x2F;bandit" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;PyCQA&#x2F;bandit</a><p>Links to codemod tools; &quot;Baby Steps into Genetic Programming&quot; <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=43617655">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=43617655</a>

&quot;AI reflex-app builder&quot; slop alert

HN

Making ast.walk 220x Faster

Comments (16)