<div dir="auto"><div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Ryan Joseph <<a href="mailto:genericptr@gmail.com">genericptr@gmail.com</a>> schrieb am Do., 27. Juni 2019, 23:50:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
> On Jun 27, 2019, at 3:09 PM, Martin <<a href="mailto:fpc@mfriebe.de" target="_blank" rel="noreferrer">fpc@mfriebe.de</a>> wrote:<br>
> <br>
> The below compiles, and writes<br>
> 1 2<br>
> <br>
> Are indexes to properties intentionally allowed to take "var param"?<br>
> Btw it even compiles with an "out" param.<br>
<br>
That sounds like a bug or something that should be prevented. I just found out default properties allowed overloading by accidental means so this may be another similar matter. Those should maybe be prevented also but that could break existing code.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">If it's a bug (what I do indeed think of this and the other bug you mentioned) it's considered acceptable to break backwards compatibility. After all we wouldn't be able to fix essentially anything as some code out there might rely on the behavior. </div><div dir="auto"><br></div><div dir="auto">Regards, </div><div dir="auto">Sven </div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote></div></div></div>