Jarc is designed to follow the Arc philosophy. I'm trying to get away from the Java philosophy! ;-)
Good point about Arc letting users make mistakes. Jarc shouldn't go out of its way to avoid coding mistakes, but given two choices considering which might generate less coding mistakes seems a valid consideration.
But the driver is really that I want the compiler to generate the fastest code possible. Minimizing coding mistakes is a post-hoc rationalization.
Since the compiler doesn't (currently) do any type inference, I have to make a choice.
