Re: Beta D 2.070.0-b1
On Monday, 11 January 2016 at 16:24:56 UTC, ponce wrote: it builds with flags -release -inline -O -w BUT NOT -unittest Makes sense https://github.com/D-Programming-Language/dub/issues/747. The compiler does check assertions in unittest blocks even in release builds, right? It's really trivial to add so you might have a try yourself https://github.com/D-Programming-Language/dub/blob/3ab683b023bd58dd101e110cf2f6199911eb7477/source/dub/package_.d#L307. In the meantime it's possible to define a custom build type http://code.dlang.org/package-format?lang=json#build-types.
Re: Beta D 2.070.0-b1
On Sunday, 3 January 2016 at 19:24:57 UTC, Martin Nowak wrote: First beta for the 2.070.0 release. Still a few things missing from the changelog, there is a new package std.experimental.ndslice, and native (DWARF based) exception handling on linux. http://dlang.org/download.html#dmd_beta http://dlang.org/changelog/2.070.0.html Please report any bugs at https://issues.dlang.org -Martin Very pleased to say that all of DlangScience worked with this beta, no regressions/breakage.
Re: Beta D 2.070.0-b1
On Mon, Jan 11, 2016 at 10:09 AM, Basile B. via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com> wrote: > On Sunday, 10 January 2016 at 23:58:38 UTC, Martin Nowak wrote: > >> On 01/03/2016 08:24 PM, Martin Nowak wrote: >> >>> Please report any bugs at https://issues.dlang.org >>> >> >> Please test the beta. >> > > Copy that. I've done what I usually do when a RC is announced and found > nothing except a small problem in unDead which was actually even not a > regression. > > Maybe there's not much feedback because there's not much problem. ;p > Yeah, I've been testing and haven't found anything broken.
Re: Beta D 2.070.0-b1
On Mon, Jan 11, 2016 at 10:15 AM, Rory McGuirewrote: > > > On Mon, Jan 11, 2016 at 10:09 AM, Basile B. via Digitalmars-d-announce < > digitalmars-d-announce@puremagic.com> wrote: > >> On Sunday, 10 January 2016 at 23:58:38 UTC, Martin Nowak wrote: >> >>> On 01/03/2016 08:24 PM, Martin Nowak wrote: >>> Please report any bugs at https://issues.dlang.org >>> >>> Please test the beta. >>> >> >> Copy that. I've done what I usually do when a RC is announced and found >> nothing except a small problem in unDead which was actually even not a >> regression. >> >> Maybe there's not much feedback because there's not much problem. ;p >> > > Yeah, I've been testing and haven't found anything broken. > :) had to say it didn't I. I now have a "out of memory" error from dmd on one of my projects. I have 16GB of ram and 2.069 doesn't do this. I'll try dustmite.
Re: Beta D 2.070.0-b1
On 2016-01-11 00:58, Martin Nowak wrote: Please test the beta. The introduction of "message" in Throwable is a breaking change [1], but I guess it's not worth reporting an issue for. [1] Error: class tango.text.xml.SaxParser.SAXException use of object.Throwable.message() is hidden by SAXException; use 'alias message = Throwable.message;' to introduce base class overload set -- /Jacob Carlborg
Re: Beta D 2.070.0-b1
On Sunday, 10 January 2016 at 23:58:38 UTC, Martin Nowak wrote: On 01/03/2016 08:24 PM, Martin Nowak wrote: Please report any bugs at https://issues.dlang.org Please test the beta. Copy that. I've done what I usually do when a RC is announced and found nothing except a small problem in unDead which was actually even not a regression. Maybe there's not much feedback because there's not much problem. ;p
Re: Damage Control: An homage to Rampart (Alpha)
On Wednesday, 6 January 2016 at 02:39:08 UTC, rcorre wrote: I'll have to look into that. If you're saying D does that by default for debug builds -- the alpha release _is_ a debug build Sorry, it was a bit unclear. I meant that: - A console window is only meaningful in debug builds, so it should be disabled in release builds. - Debug binaries should not be published, as they are meant for development only. They execute contracts, unittests and code in "debug" statements, which slow down the app and are useless for an end-user. DMD makes a console application by default, no matter what build profile is used. Here's a relevant thread: http://www.digitalmars.com/d/archives/digitalmars/D/learn/Hide_console_of_gui_program_coded_by_gtkD_41799.html It's suggested there to use "-L/SUBSYSTEM:WINDOWS" switch in DMD command line when linking under Windows.
Re: Beta D 2.070.0-b1
On Sunday, 3 January 2016 at 19:24:57 UTC, Martin Nowak wrote: First beta for the 2.070.0 release. Still a few things missing from the changelog, there is a new package std.experimental.ndslice, and native (DWARF based) exception handling on linux. http://dlang.org/download.html#dmd_beta http://dlang.org/changelog/2.070.0.html Please report any bugs at https://issues.dlang.org -Martin Both my projects and EMSI's build and pass their tests with this beta.
Re: Beta D 2.070.0-b1
On 2016-01-11 13:40, Martin Nowak wrote: Oh it's well worth to mention any update issues, in particular if we're breaking code to introduce problematic designs. https://github.com/D-Programming-Language/druntime/pull/1445#issuecomment-170530377 Created an issue: https://issues.dlang.org/show_bug.cgi?id=1 -- /Jacob Carlborg
Re: Beta D 2.070.0-b1
On 2016-01-11 13:58, Martin Nowak wrote: If the project is well maintained and relevant, just make a PR. https://github.com/MartinNowak/project_tester/blob/dd2afea122048dbcb90d0d9b637d31134a6a82ce/projects.xml#L94 I had Tango in mind. But one might argue that it's not relevant and not well maintained. But there's a couple of reasons why I think it would be good to test it: * It's pretty conservatively written. No new fancy feature, or features that might be considered experimental. This is a good test base for finding breakage for code that has been working for years, the core features * It doesn't get any new development, which means that the only likely reason for the code to not compile is because of a breaking change (accidental or intentional) * Basically every single release of DMD during last couple of years has caused at least one breakage in Tango -- /Jacob Carlborg
Re: Beta D 2.070.0-b1
On Monday, 11 January 2016 at 07:56:18 UTC, Jacob Carlborg wrote: On 2016-01-11 00:58, Martin Nowak wrote: Please test the beta. The introduction of "message" in Throwable is a breaking change [1], but I guess it's not worth reporting an issue for. Oh it's well worth to mention any update issues, in particular if we're breaking code to introduce problematic designs. https://github.com/D-Programming-Language/druntime/pull/1445#issuecomment-170530377
Re: Beta D 2.070.0-b1
On 01/11/2016 08:37 AM, Jacob Carlborg wrote: > On 2016-01-11 00:58, Martin Nowak wrote: > >> [¹]: https://github.com/MartinNowak/project_tester > > Can one request for adding projects to this? > If the project is well maintained and relevant, just make a PR. https://github.com/MartinNowak/project_tester/blob/dd2afea122048dbcb90d0d9b637d31134a6a82ce/projects.xml#L94
Re: Beta D 2.070.0-b1
On Sunday, 10 January 2016 at 23:58:38 UTC, Martin Nowak wrote: In case you don't already use Travis-CI or something similar, you should start doing so. Testing the latest beta in Travis-CI is as simple as adding dmd-2.070.0-b1 to your .travis.yml [³] (and we'll soon make it even easier adding support for dmd-beta and dmd-nightly). I fear there are more regressions that people can test for. Currently we can't "dub test" release builds trough DUB. If you do: dub test mypackage it builds with flags -g -unittest -w -debug. (like a -b debug build + the -unittest flag) But if you do: dub test mypackage -b release it builds with flags -release -inline -O -w BUT NOT -unittest Currently we can only "dub test" debug builds without anything dangerous. Since a number of regressions are in the backend, that could be useful if DUB would let us test release builds in Travis-CI.
Re: Beta D 2.070.0-b1
On Monday, 11 January 2016 at 16:24:56 UTC, ponce wrote: On Sunday, 10 January 2016 at 23:58:38 UTC, Martin Nowak wrote: In case you don't already use Travis-CI or something similar, you should start doing so. Testing the latest beta in Travis-CI is as simple as adding dmd-2.070.0-b1 to your .travis.yml [³] (and we'll soon make it even easier adding support for dmd-beta and dmd-nightly). I fear there are more regressions that people can test for. Currently we can't "dub test" release builds trough DUB. If you do: dub test mypackage it builds with flags -g -unittest -w -debug. (like a -b debug build + the -unittest flag) But if you do: dub test mypackage -b release it builds with flags -release -inline -O -w BUT NOT -unittest Currently we can only "dub test" debug builds without anything dangerous. Since a number of regressions are in the backend, that could be useful if DUB would let us test release builds in Travis-CI. From my side, when I test a DMD release I just open 1 by 1 the things in metad (https://github.com/BBasile/metad/tree/master/repos) ,compile them, some of the projects have a unittest "config" and I run it as well. It's clear that there's a risk of compilation success because templates are not instantiated... Latest two rlz i've found regressions like that but this time it's ok. Regressions for 2.070 must be on very edgy things.
Re: Beta D 2.070.0-b1
On Mon, Jan 11, 2016 at 11:26 AM, Rory McGuirewrote: > On Mon, Jan 11, 2016 at 10:15 AM, Rory McGuire > wrote: > >> >> >> On Mon, Jan 11, 2016 at 10:09 AM, Basile B. via Digitalmars-d-announce < >> digitalmars-d-announce@puremagic.com> wrote: >> >>> On Sunday, 10 January 2016 at 23:58:38 UTC, Martin Nowak wrote: >>> On 01/03/2016 08:24 PM, Martin Nowak wrote: > Please report any bugs at https://issues.dlang.org > Please test the beta. >>> >>> Copy that. I've done what I usually do when a RC is announced and found >>> nothing except a small problem in unDead which was actually even not a >>> regression. >>> >>> Maybe there's not much feedback because there's not much problem. ;p >>> >> >> Yeah, I've been testing and haven't found anything broken. >> > > :) had to say it didn't I. > > I now have a "out of memory" error from dmd on one of my projects. I have > 16GB of ram and 2.069 doesn't do this. I'll try dustmite. > > > I'm building with dub and this only happened once, I've tried using --force and I still don't get that error.