DConf 2026 in London
dconf.org
DConf 2026 in London
1–10 of 71 posts
Re: DConf 2026 in London
#2Re: DConf 2026 in London
#3Edit: Also would be nice to adopt move and copy semantics even closer to C++ and maybe need less explicit moves, and ideally less mess with calling __xdtor when trying to do RAII
Re: DConf 2026 in London
#4Re: DConf 2026 in London
#5Good language.
Re: DConf 2026 in London
#6I haven't announced my keynote yet, but it's about various ways of handling errors and their tradeoffs. This has inspired some spirited debate in the D forums! I'm looking forward to engaging with everyone.
Edit: I think it was called "Herbception"s after Herb Sutter, and it really sounded like a good idea to me
Re: DConf 2026 in London
#7I haven't announced my keynote yet, but it's about various ways of handling errors and their tradeoffs. This has inspired some spirited debate in the D forums! I'm looking forward to engaging with everyone.
Re: DConf 2026 in London
#8Re: DConf 2026 in London
#9I haven't announced my keynote yet, but it's about various ways of handling errors and their tradeoffs. This has inspired some spirited debate in the D forums! I'm looking forward to engaging with everyone.
Going to include the common lisp condition system in the comparison?
I can never get past the ugly syntax.
Re: DConf 2026 in London
#10I haven't announced my keynote yet, but it's about various ways of handling errors and their tradeoffs. This has inspired some spirited debate in the D forums! I'm looking forward to engaging with everyone.
Ages ago in C++ there was the hope of having the standard library give more error codes and use error values instead of full exceptions. Zig has some excellent innovations in that direction, any hope of that in D? Edit: I think it was called "Herbception"s after Herb Sutter, and it really sounded like a good idea to me
I used to be a big fan of C++ exceptions, but eventually soured on it for various reasons. Here's an article partially addressing it from a while back: