aG0aep6G

This doesn't seem to fix much. It just changes what kind of expression gets miscompiled. Adapted test case (also made it `-betterC`, because getting a 32-bit Phobos is too much...

With this change, compilers would still be allowed to leave the variable uninitialized, right? That means using uninitialized values would be allowed in D (as long as they're not interpreted...

> This code uses unsafe calls previously that may be considered undefined behaviour too because those calls don't provide a safe interface. Not having a safe interface doesn't mean every...

> > Not having a safe interface doesn't mean every call can be considered undefined behavior. > > True, but there's a possibility. ("that may be considered undefined behaviour") No,...

> ```d > auto right(Range)(Range r) > if(isInputRange!Range && is(ElementType!Range : int)) > { import core.stdc.stdlib; > > auto ptr = (() @trusted => malloc(10))(); > scope(exit) () @trusted {ptr.free;}();...

> This is a problem with the language spec, not the code. An immediately-invoked `@trusted` lambda does not need to have a safe interface in order to be memory-safe at...

> > Also, I'm not convinced that treating `@trusted` that way is a good idea. It makes `@trusted` even more complicated. It adds a gotcha: one cannot simply refactor a...

> But since it's still just a plan, I think in the short run it's just best to say that the safe interface requirement applies only for non-local symbols. That's...

This is an alarmingly low-effort and low-quality PR. A discussion thread with hundreds of messages of different authors displaying different opinions does not make a good rationale.

How about generating both dot-prefixed and non-prefixed anchors via `DDOC_ANCHOR`? I.e.: ``` DDOC_PSYMBOL = $(SPANC ddoc_psymbol, $0) DDOC_ANCHOR = $(ADEF .$1)$(ADEF $1)$(DIVCID quickindex, quickindex.$1, ) ``` This should get us...