@exelotl:
> [exceptions] seem like the lest-terrible tool for the job, a happy medium
> between being forced to check things vs. having to remember to check things.
Well, with an option/result you can always drop ("unwrap") it. This is cool
because now ignoring a possible error becomes explicit.
@TiffanyR:
> I'm no language designer, but if there is anything that can be done to
> simplify the syntax and remove unnecessary information - the better.
The hard part is deciding what's unnecessary information. Having a developed
type system and hiding it as much as possible leads to ambiguous code, IMO.
> 1b. Remove any use of "/" (except for division) to use a period (".")
> instead. E.g.
This goes against the habit of relying on the operator/function overloading by
default. Don't know if I agree with this practice or not though.
* * *
Another breaking change would be fixing **slices to return openArrays**. Much
more intuitive and I think most uses don't need a copy anyway.
