On Friday, 26 May 2017 at 13:23:20 UTC, Jason King wrote:
wanted to fix a problem with the underlying system. Trying to
build
something on top of an unstable ABI is building your
foundations on sand.
All I’m saying is if no attention is going to be paid to this
(it doesn’t mean you can’t change the ABI, but it needs to be
managed it better than ‘whoops!’), just stop claiming the
systems bit and stay up stack where this isn’t a problem.
There is some truth to this as BeOS used C++, and ABI was a
concern, but it really depends on the context. D has a too big
runtime and too many runtime dependent features to be classified
as a low level language anyway, though...
