Glad to announce the first beta for the 2.083.0 release, ♥ to the 48 contributors for this release.

http://dlang.org/download.html#dmd_beta http://dlang.org/changelog/2.083.0.html

As usual please report any bugs at https://issues.dlang.org

- ----

Highlights:

BetterC build option in dub -
https://dlang.org/changelog/2.083.0.html#betterC_build_option
CppRuntime_* version identifiers -
https://dlang.org/changelog/2.083.0.html#cppVersions
New isZeroInit trait - https://dlang.org/changelog/2.083.0.html#isZeroIn
it
DUB_PACKAGE_VERSION environment variable -
https://dlang.org/changelog/2.083.0.html#env_var_package_version

- -Martin

On Wednesday, 17 October 2018 at 12:14:55 UTC, Martin Nowak wrote:
> Glad to announce the first beta for the 2.083.0 release, ♥ to the 48 contributors for this release.
>
> http://dlang.org/download.html#dmd_beta http://dlang.org/changelog/2.083.0.html

Wait, why does each get a special bailout? Doesn't until full that role?

On Wednesday, 17 October 2018 at 12:14:55 UTC, Martin Nowak wrote:
> Glad to announce the first beta for the 2.083.0 release, ♥ to the 48 contributors for this release.

Thanks!

> CppRuntime_* version identifiers -
> https://dlang.org/changelog/2.083.0.html#cppVersions

When is this different from the corresponding CRuntime version?

> DUB_PACKAGE_VERSION environment variable -
> https://dlang.org/changelog/2.083.0.html#env_var_package_version

The documentation for this one seems rather sparse.

- Is the environment variable set or read by Dub?
- What is the exact syntax for its contents?
- How does it affect the build process?
- What are some potential use cases?

On Wednesday, 17 October 2018 at 15:18:43 UTC, Vladimir Panteleev wrote:
> On Wednesday, 17 October 2018 at 12:14:55 UTC, Martin Nowak wrote:
>> Glad to announce the first beta for the 2.083.0 release, ♥ to the 48 contributors for this release.
>
> Thanks!
>
>> CppRuntime_* version identifiers -
>> https://dlang.org/changelog/2.083.0.html#cppVersions
>
> When is this different from the corresponding CRuntime version?
>
>> DUB_PACKAGE_VERSION environment variable -
>> https://dlang.org/changelog/2.083.0.html#env_var_package_version
>
> The documentation for this one seems rather sparse.
>
> - Is the environment variable set or read by Dub?
> - What is the exact syntax for its contents?
> - How does it affect the build process?
> - What are some potential use cases?

The new variable does not affect the build process. It is set by dub and has the content you also see by dub describe command.
In a pre command you can have a script which writes the content of the variable to a constant within D module. Therefore it becomes very easy to compile the version of your application into your application.

Kind regards
Andre

On Wednesday, 17 October 2018 at 12:14:55 UTC, Martin Nowak wrote:
> Glad to announce the first beta for the 2.083.0 release, ♥ to

BTW, title says Beta 2.082.0 :)

On Wednesday, 17 October 2018 at 14:02:20 UTC, Jesse Phillips wrote:
> Wait, why does each get a special bailout? Doesn't until full that role?

`until` is lazy. We could have `doUntil` instead, which would be eager and would return a boolean indicating whether to continue. We could all write `someRange.until!condition.each!func`. That's going to be clearer sometimes and less clear other times. So now we have options.

On Wednesday, 17 October 2018 at 15:18:43 UTC, Vladimir Panteleev wrote:
> On Wednesday, 17 October 2018 at 12:14:55 UTC, Martin Nowak wrote:
>> Glad to announce the first beta for the 2.083.0 release, ♥ to the 48 contributors for this release.
>
> Thanks!
>
>> CppRuntime_* version identifiers -
>> https://dlang.org/changelog/2.083.0.html#cppVersions
>
> When is this different from the corresponding CRuntime version?

CppRuntime is per compiler, CRuntime is per system.

An example: on linux linking with Clang's C++ lib, the CppRuntime is CppRuntime_Clang and the CRuntime is CRuntime_Glibc.

On Wednesday, 17 October 2018 at 16:14:14 UTC, Neia Neutuladh wrote:
> On Wednesday, 17 October 2018 at 14:02:20 UTC, Jesse Phillips wrote:
>> Wait, why does each get a special bailout? Doesn't until full that role?
>
> `until` is lazy. We could have `doUntil` instead, which would be eager and would return a boolean indicating whether to continue. We could all write `someRange.until!condition.each!func`. That's going to be clearer sometimes and less clear other times. So now we have options.

    auto arr = [10, 20, 30];
    arr.until!(x=>n==20).each!(n => arr ~= n);

Ok, I can see why that doesn't work.

On Wednesday, 17 October 2018 at 12:14:55 UTC, Martin Nowak wrote:
> Glad to announce the first beta for the 2.083.0 release, ♥ to the 48 contributors for this release.
>
> http://dlang.org/download.html#dmd_beta http://dlang.org/changelog/2.083.0.html
>
> As usual please report any bugs at https://issues.dlang.org
>
> - ----
>
> Highlights:
>
> BetterC build option in dub -
> https://dlang.org/changelog/2.083.0.html#betterC_build_option
> CppRuntime_* version identifiers -
> https://dlang.org/changelog/2.083.0.html#cppVersions
> New isZeroInit trait - https://dlang.org/changelog/2.083.0.html#isZeroIn
> it
> DUB_PACKAGE_VERSION environment variable -
> https://dlang.org/changelog/2.083.0.html#env_var_package_version
>
> - -Martin

Thanks!

Is too much asking to take a look on this bug?
https://issues.dlang.org/show_bug.cgi?id=18457
:)

On 10/17/18 2:14 PM, Martin Nowak wrote:
> Glad to announce the first beta for the 2.083.0 release

Second beta live now

> http://dlang.org/download.html#dmd_beta http://dlang.org/changelog/2.083.0.html