On Wednesday, 15 June 2016 at 19:39:59 UTC, Konstantin wrote:
Well I’m not sure about the 5% (MS says their write barrier overhead is comparable to the cost of a simple method call, namely 6.4ns: https://msdn.microsoft.com/en-us/library/ms973852.aspx), but yeah, there’s some tradeoff, for having a good GC.
Even 1% overhead is unacceptable. Again, it's not reasonable for a systems language to have people pay for things they're not using.
Write barriers will come to D over Walter's dead body.
By the way, Go implemented those barriers in version 1.5 a year ago: https://blog.golang.org/go15gc
Go has no allocation strategies but the GC, so that point is moot.
