Manu Evans
Manu Evans
Perhaps we can we spin off a separate issue for looking into memory consumption? That's kinda OT here.
I don't think this was a question of optimisation, but a question of strategy, or better, and OOTB recommendation for users. I don't think we're there. I think this is...
Yeah I resolved the issue locally, I was just letting you know. Do you know the cost to renew the certificate? Dlang foundation will probably sponsor it.
I mean, it's a supported target, but it's low priority. That aside though, what's with `extern(D)`? That looks broken too... I never saw anywhere that D has a custom ABI?
``` The extern (C) and extern (D) calling convention matches the C calling convention used by the supported C compiler on the host system. Except that the extern (D) calling...
But yeah, `fastcall` is a common ABI, I kinda need it. Otherwise I gotta write shim's and stuff, which rather defeats the purpose of `fastcall` :P
Why discourage it? Why not make it work good?
> you don't even get an error when specifying an invalid one :D This doesn't seem insurmountable :P
> IMO not worth the effort, uninteresting 32-bit x86 legacy stuff. Well, it seems to work; `fastcc` did what I expect... so, why shouldn't I use it exactly?
That said though, the weird case where it was still `extern(D)` but the register randomly swapped over... that's really weird!