Niko , what about the performance of these polymorphic functions ? Even C++ virtual calls bite when you have calls to a different compilation unit compared to a good java run time ( mainly due to polymorphic inline caches). And how do you handle module traits there are some nasty issue here with Haskell.
You still confident you can avoid the OO issues bitC hit when they tried to add OO calls to traits eg http://www.coyotos.org/pipermail/bitc-dev/2012-March/003300.html Ben On Thu, Oct 11, 2012 at 12:44 PM, Niko Matsakis <[email protected]> wrote: > > > Niko Matsakis wrote: > >> Based on our last meeting, there seems to be general agreement towards a >> system that allows methods to be imported as standalone functions that take >> the receiver as first argument as well [1]. >> > > Actually, it occurs to me that we only discussed these kinds of imports in > the context of static fns. But in any case I am a fan of permitting any > function defined in an impl to be imported and used as a standalone > function, and I think I am not alone in this. =) > > > Niko > > ______________________________**_________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/**listinfo/rust-dev<https://mail.mozilla.org/listinfo/rust-dev> >
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
