numeral

For numeral types, it makes the sum of the operands.

That's wrong in a couple ways: "Arabic numerals" aren't Arabic.

In blocks of text, not in tabular formatting, the changes in the numeral heights can help carry the eye along.

Fonts where you can't tell the difference between capital eye, lowercase ell, and numeral one are a pain in the ass.

Technically speaking, the roman numeral "M" stands for one thousand.

If anything, all fixed height numerals are the newer invention.

No, iterate is just a helper function to convert a Haskell integer to a Church numeral.

Since identifiers can't begin with a numeral, there's no way to shadow a valid use of a complex number this way.

A poor example given that I'm simulating old-style numerals, but you get the idea.

There are some people with similar visualizations to mine, and someone who perceives a year as a giant numeral '7'!

I remember how hard I laughed when I noticed that LC's false function is the same as the Church-encoded numeral for zero.

Apple is embracing three numeral technology while their competitors are stuck in the two numeral age.

Interesting that if we used a base-12 numeral system then this would be immediately obvious.

If the inputs were directly represented as Church numerals, it wouldn't be needed and you'd just replace every instance of iterate n with n itself.

It underlies the predecessor/decrement function for Church numerals which the author of the article presents but chooses not to explain; the idea is simple, if rather inspired.

Apple's ability to increase numerals a full fifty percent when pundits were expecting a mere incremental refresh is perhaps the most amazing news of 2013.

The prevailing numeral system being replaced, Roman numerals, also placed the most significant digit on the left, so it's unlikely that this was something that was simply forgotten.