> > > Not if the runtime environment is CLR. > C++ in the CLR is not standard C++ all the types needs to be changed and there is many things you cant do with pure mode so it still a significant amount of work. You can embed native C++ in the assemblies but im not really sure how this works ( i looked it up once and found it simpler to wrap it in a c api) , likewise the link to external libs especially the marshalling of non trivial types...though its likely that its the easiest way for any GC platform. It maybe that mapping it to a rust trait with methods ( which have a this pointer) would be better , simply because there may be no GC marshaling or pinning needed.
I really like the CLR but its worth restating that mono is substandard , its not as reliable and maybe 30% worse performance. And mono does not support C++ , mixed assemblies etc . I did some code to add capabilities to the run time and support the new Windows Store app API and was pretty shocked to find the JIT had not changed in 7 years.. no polymorphic in line caches etc.. That said the Xamarin guys are working on Android /ios runtimes which are more constrained and they make money from it so there is a lot more incentive. <snip> > > I agree with you that prevalence of templates is rising, but I *suspect* > that most of those are in a small number of key libraries. Yes , mainly boost / some collections , but its getting worse i see some stuff in the newer libs which give higher order support ( lambdas etc) Regards, Ben _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
