On Wed, Mar 10, 2010 at 1:18 AM, Michal Suchanek <[email protected]> wrote: > I would pose the question differently: is there a use case for shallow > read-only.?
Funny how this keeps coming up in conversations over the last few weeks. Short answer: yes. You cannot type the RHS of an assignment or initialization without the ability to express shallow read only. Setting that issue aside, it's also important to be able to call code written in other languages, and this requires that we be able to express things like: SomeStruct *const which is shallow read-only. _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
