jaredpar / docs Goto Github PK

In reference to https://github.com/jaredpar/docs/blob/master/slices/prototype.md

I am very concerned that we are launching into a prototype which seems at least moderately expensive (changing the underlying representation of an array, adding new JIT optimizations to overcome the perf loss from that new representation, dealing with the breaking nature of the change etc), without being clear about the benefit and the alternatives.

In particular, the proposal suggest that we simply make arrays have slice capabilities. However there is a very reasonable alternative (which by the way is used by Swift), that makes Slice a type distinct from arrays.

This solution is significantly cheaper (no runtime changes are needed and thus no breaking changes or need to depend on particular versions of the runtime).

We need to articulate that solution as well as indicate when the two solutions differ and have an discussions/evaluation on the value of that difference.

Proceeding with prototype without first making clear what the BENEFIT of that prototype's ADVANTAGES of that prototype is over the other very reasonable alternatives is premature.