Scientific computing and parallel computing C++23/C++26
iamthewilsonator at hotmail.com
Fri Jan 14 00:39:02 UTC 2022
On Thursday, 13 January 2022 at 21:06:45 UTC, Ola Fosheim Grøstad
> On Thursday, 13 January 2022 at 20:38:19 UTC, Bruce Carneal
>> I know, right? Ridiculously big opportunity/effort ratio for
>> dlang and near zero awareness...
> If dcompute is here to stay, why not put it in the official
> documentation for D as an "optional" part of the spec?
> I honestly assumed that it was unsupported and close to dead as
> I had not heard much about it for a long time.
I suppose that's my fault for not marketing more, the code
generation is tested in LDC's CI pipelines so that is unlikely to
break, and the library is built on slow moving APIs that are also
unlikely to break. Just because it doesn't get a lot of commits
doesn't mean its going to stop working.
As for specification, I think that would be a wasted effort and
too constraining. On the compiler side, it is mostly using the
existing LDC infrastructure with (more than) a few hacks to get
everything to stick together, and it is heavily dependant on LDC
and LLVM internals to be part of the D spec. On the runtime side
of it, I fear specification would either be too constraining or
end up out of sync with the implementation.
More information about the Digitalmars-d