On Monday, 19 September 2016 at 10:07:06 UTC, Stefan Koch wrote:
Compiling all of phobos does not crash my engine anymore!
Great work! Keep up still!
On Monday, 19 September 2016 at 18:05:34 UTC, Lurker wrote:
Good news anyway! Do you have any preliminary results or goals
and expectations that you are going to achieve with your
rework? Is it mostly perf/memory improvements, are there any
new features that this rework will unlock?
Thanks
On Monday, 19 September 2016 at 13:08:34 UTC, Martin Nowak wrote:
On Monday, 19 September 2016 at 12:26:21 UTC, Jack Stouffer
wrote:
On a slightly related note, I think it would be a good idea to
branch off 2.072 and start beta testing right away, as it's
been five months since the last point
On Monday, 19 September 2016 at 12:26:21 UTC, Jack Stouffer wrote:
On a slightly related note, I think it would be a good idea to
branch off 2.072 and start beta testing right away, as it's
been five months since the last point release, and A LOT has
changed since then. I fear that we may see
On Monday, 19 September 2016 at 11:08:33 UTC, Martin Nowak wrote:
Glad to announce D 2.071.2.
http://dlang.org/download.html
This point release fixes many issues with the new lookup and
import rules. It should be used as a stopgap version when
updating older code. The deprecations, the old
Glad to announce D 2.071.2.
http://dlang.org/download.html
This point release fixes many issues with the new lookup and import
rules. It should be used as a stopgap version when updating older code.
The deprecations, the old access checks, and the
-transition=import/checkimports switches are
On Thursday, 8 September 2016 at 18:54:52 UTC, Stefan Koch wrote:
On Thursday, 8 September 2016 at 13:11:23 UTC, Stefan Koch
wrote:
On Thursday, 8 September 2016 at 10:44:55 UTC, Stefan Koch
wrote:
compiling parts of phobos does no longer crash the new engine.
However it still produces
On Sunday, 18 September 2016 at 09:10:41 UTC, Johan Engelen wrote:
I think LDC has the same problems (template instances are
emitted in the first module not the one that needed the
instantiation?). Knowing this, you may be able to set up a case
where things break, but I think it would have to
