Am Wed, 16 Jul 2014 11:49:21 -0700 schrieb Walter Bright <[email protected]>:
> On 7/16/2014 7:14 AM, Daniel Murphy wrote: > > Intrinsics get us away from our current 'there is no portable way > > to do this' situation. They are _trivial_ to implement for any of > > the compilers. I have complete faith that it is possible to make a > > performant wrapper for both the single-register read/write and the > > struct pattern you posted. And if I'm wrong > > - we can add a volatile type modifier later! > > I'll add that if it turns out we can't do a wrapper because of some > limitations/bugs in D's expressiveness, that is the problem with D we > need to fix, not adding another type modifier. > > It all comes down to leverage. Making user defined types more capable > has far, far more productive leverage than welding specifics into the > compiler. > I'll take this as you pre-approve all the mentioned extensions? * way to disable typeinfo for struct * way to disable initializer * force inlining * (way to omit copy constructor function / force inline)
