On Fri, 31 Dec 2010 10:11:02 -0500, bearophile
wrote:
Steven Schveighoffer:
so even though I feel this is a bug (it should be silently ignored),
Generally silently ignoring attributes is exactly the opposite you want
from a modern compiler. See bug
3934.
In this case though, you are
Steven Schveighoffer:
> so even though I feel this is a bug (it should be silently ignored),
Generally silently ignoring attributes is exactly the opposite you want from a
modern compiler. See bug
3934.
Bye,
bearophile
On Fri, 31 Dec 2010 09:09:23 -0500, szali wrote:
BTW, this list is generally not used for questions (it's auto-generated
from bugzilla reports), d.learn is a better place, but no worries, here
are your answers:
In one of my classes, I created two overloads to opIndexAssign (the
second one
In one of my classes, I created two overloads to opIndexAssign (the
second one was made for better performance, because in most cases
only one index is used):
public final T opIndexAssign(T value, int[] args ...)
public final T opIndexAssign(T value, int i)
These are allowed by the compiler. But
