Quantifiers

The quantifier has a really simple structure. What make its complicated is the number of usages it has. You can loop for an amount of repetitions, calories, etc. By the way, there is two special behaviors when using a list of values or time.

Repetitions

This one is the easiest and the more frequent usage you will encountered.

10rep burpees

Energy

Some torture machines uses an energy unit to measure the activity (row, air-bike, etc.).

10cal row

Length

Some exercises had an objective measured in length.

250ft handstand walk

1.6km run

Weight

This one is a little bit special and unusual. But there is a use-case for it. Just imagine a WOD that tells you to lift 1000kg in backsquat. You can do 10 repetitions with 100kg or 20 repetitions with 50kg.

1000kg backsquat (with a bar of: ? (weight))

Time

Some exercises such as the handstand hold or the plank had an objective measured in time.

0:30 handstand hold

20s plank

List

A list is a special expression that can be used as a quantifier. It has a special syntax that give it superpowers. It act as a loop and will go through each values until it reach the end. The current value can be exported as the variable you want.

[21, 15, 9] as @n
    @n thrusters (with a bar of: 95lb)
    @n pull-ups

This example defines the benchmark WOD Fran. It would have been defined this way:

21 thrusters (with a bar of: 95lb)
21 pull-ups
15 thrusters (with a bar of: 95lb)
15 pull-ups
9 thrusters (with a bar of: 95lb)
9 pull-ups

But the program is less concise and the 21, 15, 9 structure is well-known and understood. By the way, you should never prefer the concision over the readability of the program. There are many cases where the full description of the WOD is preferable to the concise one.