Because detecting that requires code flow analysis.<div>Note that it is completely different from CTFE.<div><div class="gmail_extra"><br></div><div class="gmail_extra">Kenji Hara<br><br><div class="gmail_quote">2012/12/13 Pacoup <span dir="ltr">&lt;<a href="mailto:etiennelg@gmail.com" target="_blank">etiennelg@gmail.com</a>&gt;</span><br>
<blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">
On Thursday, 13 December 2012 at 04:26:52 UTC, Mehrdad wrote:<br>
<blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
It&#39;s C++ philosophy imposed on the C#-like aspects of the language.<br>
</blockquote>
<br></div>
That&#39;s not a rationale for not having bounds checking on dynamic arrays at compile time. How is this making the language better? Is there a technical limitation which explains this?<br>
</blockquote></div><br></div></div></div>