EMPTY? none

This is not a new idea... it's a nag.

Code like this pops up often:

if all [not none? value not empty? value] [...]

If we allow EMPTY? on none! then we could simply write:

if not empty? value [...]

I'm inclined to add it... unless you shout loudly really soon.

Why? This pattern happens often. FOREACH already does it in R3.