Compiler issue with non-existent NIL conditions

This is a fruitless back-and-forth because you’re not focusing on what I’m raising, as a language user.

I consider the behavior in this example of the endless range form (2..).each a bug because it doesn’t behave as I expect and as I desire it to behave!.

You don’t care that I consider it a bug, or even just undesirable behavior, so I as a user have to bear the consequences of what I consider is a poor design decision, which can be fixed.

So there’s no point for me to discuss this anymore since I figured out how to write equivalent functional code that performs as I want.