[BAILOPAN]

KyleS: I'm open to alternate proposals but they need to have really clear semantics so they're probably best taken offline, through PM or IRC. Yours looks identical to #3 but with the introduction of a pointer type and it's not really clear what that means. On face value it could mean one of three things: (1) It means proposal #2, except that the pointer can leak a value on the stack. (2) It means proposal #4, except with a * sigil instead of @. It means proposal #3, except it adds some kind of indirection.

In terms of reading and writing elements, dynamic arrays would act identically to the existing array types. I feel pretty strongly that dynamic arrays should coerce to old-style arrays, when calling functions, for maximum compatibility.