This is true, but I avoided doing that because the parser would lose a use case (a single instance wouldn't be capable of parsing both with and without the inclusive dot). That's not one of the use cases that I've needed, but I couldn't think of a good reason why we should artificially eliminate that use case (there are two other projects, Play2 and some other OS project that stole the Play2 template compiler, that will be adopting this code, and perhaps they'll have that use case, in which case eliminating the extra object allocations would be nice :-)).