I'm going to respond to this under a new subject line, because this isn't a discussion of effects and it is a major topic in it's own right.
PLEASE let's have this conversation under that subject heading. On Thu, Aug 8, 2013 at 10:15 AM, David Jeske <[email protected]> wrote: > i propose (deep) const and shallow const effects.... > > shallow const being like c/c++ const, and (deep) const recursively > applying to any fields accessed. > > in c#, i miss const, as readonly fields don't really fill the same niche. > for example, passing a large struct as ref is much faster, but you can't > establish a policy of them not changing it.. "const ref" would be perfect, > and might not require the ref decorator when supplying the argument. > > these could be inferred within a module for convenience, but would need to > be declared at module boundaries, to avoid thebinference hamstringing > someone's module contract. > > -- > "*In science if you know what you are doing you should not be doing it. * > *In engineering if you do not know what you are doing you should not be > doing it. * > *Of course, you seldom, if ever, see either pure state.*" - Richard > Hamming > > > _______________________________________________ > bitc-dev mailing list > [email protected] > http://www.coyotos.org/mailman/listinfo/bitc-dev > >
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
