Ah, thanks. I wasn't aware of that. I should start tracking that RSS feed...
I am very concerned that single-inheritance takes the language in the wrong direction. I feel that a more mixin-oriented solution would better match Rust's traits based type system. I posted a comment the blog entry you gave, which I assume is a more appropriate venue than this thread...? Either way, I gather there's no current idiomatic pattern for this - we are waiting until some solution is agreed upon (and implemented :-) Thanks, Oren. On Mon, Nov 11, 2013 at 11:43 PM, Patrick Walton <pcwal...@mozilla.com>wrote: > On 11/12/13 5:16 AM, Oren Ben-Kiki wrote: > >> I googled around and this has been asked before several times; there are >> answers that use obsolete syntax and Rust concepts, so I thought it >> might be a good idea to revisit the issue. >> >> The basic use case is having some trait, and having some (base/mixin) >> struct implementing it. Now, one wants to have a 2nd (derived/importing) >> struct implementing the trait, based on the 1st struct implementation >> (including its data members). >> > > There are proposals for this, if I understand you correctly. This is > needed in Servo. > > http://smallcultfollowing.com/babysteps/blog/2013/10/24/ > single-inheritance/ > > Patrick >
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
