The tag is a winning criterion where the program with the least AST nodes wins. This seems like a subset of , where the program with the least operations by some definition wins.

It has one question, which looks quite similar to a typical question:

Scoring Heuristics

The following rules are typically enough to calculate the score of your program:

  • Block statements are 1 points: if, for ... in ..., while, else, etc.

  • Standalone statements are 1 point: print in Python 2, break, pass, etc.

  • Variables are 2 points

  • ...

Also, the original intent of the tag was to count a single token per statement / value / similar in a program, in an attempt to level the playing field.

So, what should we do with ?


1 Answer 1


Merge it into

Do we really need for this? Isn't this just a specific form of ?
- Martin Ender

The reason I did it this way is because the tag text for atomic-code-golf says "Atomic code golf is scored by the number of tokens of your program," and that's not the same as this, though perhaps only a pretty small amount.
- isaacg

Given that:

  1. there have been no other questions in over five years and
  2. the OP admits that it's nearly the same as and
  3. it's since been retagged as

I don't think the slight difference in scoring from regular makes enough of a difference to keep a separate tag. This challenge is a variant of , the same way that a challenge that counts box-drawing characters as one byte is a variant of , or that a challenge about xiangqi is a variant of .

It might be worth updating the tag wiki to explicitly include this kind of variant.

  • 7
    \$\begingroup\$ And even if it was totally separate from atomic-code-golf, an OWC tag that applies to exactly one question is pointless to have anyway since code-challenge exists \$\endgroup\$ Commented Feb 14, 2022 at 3:04

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .