On Monday, 20 August 2012 at 15:42:50 UTC, Jonathan M Davis wrote:
On Monday, August 20, 2012 12:44:40 monarch_dodra wrote:
Except that generally assert does the job just fine. The only
reason that -
noboundscheck is any different really is the fact that bounds
checking is left
on in @safe code even with -release. It just seems overkill to
me try and have
user-defined types act the same way. It's arguably bad enough
that arrays work
this way.
If you want control user-defined types with a
version(noboundscheck), then
create an enhancement request, and maybe Walter will think that
it's a good
idea. I don't know. It seems completely unnecessary to me, but
that doesn't
mean that it won't happen.
- Jonathan M Davis
Oh yeah... noboundscheck is not as simple as just doing
"-noboundscheck".
You are probably right, this would bring more harm than good.
