[removing the chapel-bugs list] On 01/03/2014 07:40 AM, Michael P. Ferguson wrote:
> [...] > Lastly, I think it's confusing that in this one way we have a structural type > system, > where the rest of the Chapel type system is nominative. [...] I agree. Towards that end, we all have played with the idea of a "use" clause inside a record or class declaration, which incorporates the other record's fields but does not create a subtype of that record. To be fair, a structural type system has ease-of-programming aka productivity benefits, and I think Brad likes those. So I'd say that ideally we'd provide them in Chapel as well. In which case they need to be clearly distinguished from the nominative universe. Maybe they could be based on Michael&Jeremy's interfaces? Vass ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
