[OT] - C++ exceptions are becoming more and more problematic
IGotD-
nise at nise.com
Thu Feb 24 10:06:24 UTC 2022
On Thursday, 24 February 2022 at 08:08:49 UTC, Paulo Pinto wrote:
>
> They aren't going anywhere, most of Herb's latest papers seem
> like ideas how the language could be improved upon, but beyond
> the original paper, presentation at CppCon and eventually some
> prototype available on Compiler Explorer, little more has
> happened.
>
> I might be wrong here, but from C++ mailings it is clear
> nothing is happening with those papers.
>
> Also in regards to exceptions, Bjarne has a paper where he
> criticizes the current compiler implementations for leaving
> performance improvements on the table by not wanting to break
> existing ABIs, while arguing against Herb's approach.
>
> "C++ exceptions and alternatives"
>
> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1947r0.pdf
That's a problem for D because I suggest that we copy whatever
C++ decides to implement. The reason is that the solution is
probably going to be good enough for D. Using the C++ solution
also ensures FFI compatibility. Associated with the new C++ error
handling is going to be an ABI change (for every CPU
architecture) and that the D project would create its own bespoke
ABI is a lot of work which might not play well with C++ or other
SW.
More information about the Digitalmars-d
mailing list