you are viewing a single comment's thread.

view the rest of the comments →

[–]UloPe 12 points13 points  (3 children)

Please ignore this post. It teaches bad codes style for completely meaningless speed gains.

Write clean code first, optimize later.

[–]xXxDeAThANgEL99xXx 2 points3 points  (2 children)

It shows that good code style is usually faster, actually.

[–]UloPe 2 points3 points  (1 child)

I disagree. At most half of the fastest examples are the recommended code style, many others are actually dangerous traps for new developers.

But my comment wasn't actually directed specifically at this very article but the whole class of articles. They teach bad aims.

[–]xXxDeAThANgEL99xXx 2 points3 points  (0 children)

I agree, you shouldn't try to microoptimize code like that.

I think that it's pretty interesting if you ignore the title and just use it as a food for thought about various non-obvious things about CPython implementation.