On Saturday, 17 December 2011 at 23:31:47 UTC, Andrei Alexandrescu wrote:
Safety is also an issue. I was hoping I'd provide safety as a policy, e.g. one may choose for a given container whether they want safe or not (and presumably fast). I think it's best to postpone that policy and focus for now on defining safe containers with safe ranges. This precludes e.g. using T[] as a range for Array!T.

Since containers are templated, why not use asserts for this, and let the user choose with -release (just as with built-in arrays)?

Reply via email to