Re: Blog post: What D got wrong
On Tuesday, 18 December 2018 at 11:25:17 UTC, Jonathan M Davis wrote: Of course, even if we _did_ have a solution for reversing attributes, slapping an attribute on the top of the module would still potentially be a maintenance problem, because it's then really easy to miss that an attribute is in effect (it's a problem that we've had on several occasions with druntime and Phobos in the few cases where attributes are mass-applied). So, there is no silver bullet here (though regardless of whether mass-applying attributes is something that should ever be considered good practice, we really should add a way to be able to reverse them). Thanks Jonathan for your elaborate explanation. I personally have no problem with the attributes which - in practice - means I don't use them much unless I want to make sure something is nogc, for example. For library designers it makes sense to be explicit. I guess that is where the trade-off kicks in. Maybe it is just a feature. We argue against specifying them because other languages are not as explicit. It does add a little noise.
Re: Blog post: What D got wrong
On Thursday, 13 December 2018 at 18:29:39 UTC, Adam D. Ruppe
wrote:
On Thursday, 13 December 2018 at 10:29:10 UTC, RazvanN wrote:
Do you honestly think that they will ever take D into account
if @safe and immutable data will be the default?
D needs to stop chasing after what you think people think they
want and just start being good for us.
The majority of my code is written pretty permissively - I like
my pointers, my gotos, my GC, my exceptions. But I'm willing to
consider the change because I actually don't think it will be
that big of a hassle, and will be better overall. I wanna show
you something:
/// Static convenience functions for common color names
nothrow pure @nogc @safe
static Color transparent() { return Color(0, 0, 0, 0); }
The attribute spam is almost longer than the function itself.
Isn't it the way forward that the compiler deduces these
attributes and fills them in automatically? All these can be
inferenced. Only when the caller wants to guarantee, say pure, it
could add it explicitly. I read somewhere that the compiler
already does this to some degree. And even the generated docs
should be able to show it.
Re: Release D 2.082.0
On Sunday, 2 September 2018 at 01:05:10 UTC, Martin Nowak wrote: http://dlang.org/changelog/2.082.0.html -Martin gdb exception catching looks pretty useful to me!
Re: GDC with D frontend 2.081.2
On Friday, 24 August 2018 at 05:35:13 UTC, Eugene Wissner wrote: I prepared GDC/GCC 7.3.0 binaries for x86-64 Linux built on Ubuntu 18.04: Thank you, this is very important work! I'll add a gdc package to GNU Guix (the packager for GNU) sometime soon.
Re: std.variant Is Everything Cool About D
Great blog. Thanks.
Re: Updated D packages in GNU Guix for x86_64-linux, i686-linux, armhf-linux
On Sunday, 11 March 2018 at 12:41:28 UTC, Johan Engelen wrote: Kai has been working recently [1] on updating LDC 0.17.x (ltsmaster) to work with LLVM 6, PowerPC, AArch64, ... You may want to take advantage of that activity to get better bootstrap compiler support for your platforms. For example by filing bug reports, or better: helping out with testing and fixing things ;-) Sure thing. Guix can support multiple versions of LLVM and build against those, so you can inject different dependencies (read versions of LLVM) in the dependency graph. I am quite keen to use the latest for my tools.
Updated D packages in GNU Guix for x86_64-linux, i686-linux, armhf-linux
The GNU package manager updated LDC to 1.7.0 which now provides x86_64-linux, see https://www.gnu.org/software/guix/packages/L/. Runtime dependencies and build are listed at https://hydra.gnu.org/build/2525193#tabs-runtime-deps, including 0.17.4 (bootstrap) and LLVM 3.8.1. LDC 0.17.4 provides x86_64-linux, i686-linux, armhf-linux. We aim to add D compilers for all supported architectures. Note that GNU Guix can run on top of all Linux distributions because it is self-contained. Guix includes all its dependencies (except the kernel) and can be removed easily.
Re: To all DConf speakers: please upload slides!
On Wednesday, 11 May 2016 at 09:17:54 UTC, Dicebot wrote: To do the editing of HD videos we need presentation slides which are currently scattered over different places. It would help a lot to have them all in github.com/dlang/dlang.org repo - please submit pull requests asap! Lightning talk slides also to be included? Mine are at http://biobeat.org/dconf2016.pdf
