On Wednesday, 15 May 2019 at 07:39:05 UTC, Walter Bright wrote:
> https://github.com/dlang/phobos/pull/6931
>
> This is a major milestone in improving the memory safety of D programming. Thanks to everyone who helped with this!
>
> Time to start compiling your projects with DIP1000, too!

For me, the forum claims that your posting time is "from the future". Does that mean that is has somehow leaked a draft and this shouldn't show yet?

About -DIP1000, I sure want to use it. But is there currently any practical way to learn it's usage without researching compiler source code?

On Wednesday, 15 May 2019 at 06:49:02 UTC, Dukc wrote:
> For me, the forum claims that your posting time is "from the future". Does that mean that is has somehow leaked a draft and this shouldn't show yet?

No, it is merged. As to why from the future, probably timezones.

On Wednesday, 15 May 2019 at 07:56:48 UTC, Walter Bright wrote:
>> About -DIP1000, I sure want to use it. But is there currently any practical way to learn it's usage without researching compiler source code?
>
> Simply add the switch -preview=dip1000 to your builds, and follow where it leads.

Bound to cause bad practices without nothing to tell why it works how it works. How do I know when I'm supposed to add `scope`? Or how to react when the compiler complains about escaping references? I have some basic image in my head formed from your DIP paper, but I read somewhere that it's outdated.

Could be worth a try even without docs, but in the long run we definitely need some explaining.

On Wednesday, 15 May 2019 at 08:26:23 UTC, Walter Bright wrote:
>
> This is a good start:
>
> http://dconf.org/2017/talks/bright.html

Ah, at least something. Thanks.

On Wednesday, 15 May 2019 at 07:56:48 UTC, Walter Bright wrote:
> On 5/14/2019 11:49 PM, Dukc wrote:
>>> Time to start compiling your projects with DIP1000, too!
>> For me, the forum claims that your posting time is "from the future". Does that mean that is has somehow leaked a draft and this shouldn't show yet?
>
> Maybe the clock is not synchronized somewhere.
>
>> About -DIP1000, I sure want to use it. But is there currently any practical way to learn it's usage without researching compiler source code?
>
> Simply add the switch -preview=dip1000 to your builds, and follow where it leads.

For reference, people need to use dmd-nightly (available tomorrow), build dmd themselves or wait until DMD 2.087 (1st of July).

Also, as most projects use Dub, the flag can be added to the dub.sdl too:

---
dflags "-preview=dip1000"
----

https://github.com/dlang/phobos/pull/6931

This is a major milestone in improving the memory safety of D programming. Thanks to everyone who helped with this!

Time to start compiling your projects with DIP1000, too!

On 5/14/2019 11:49 PM, Dukc wrote:
>> Time to start compiling your projects with DIP1000, too!
> For me, the forum claims that your posting time is "from the future". Does that mean that is has somehow leaked a draft and this shouldn't show yet?

Maybe the clock is not synchronized somewhere.

> About -DIP1000, I sure want to use it. But is there currently any practical way to learn it's usage without researching compiler source code?

Simply add the switch -preview=dip1000 to your builds, and follow where it leads.

On Wednesday, 15 May 2019 at 07:39:05 UTC, Walter Bright wrote:
> https://github.com/dlang/phobos/pull/6931
>
> This is a major milestone in improving the memory safety of D programming. Thanks to everyone who helped with this!
>
> Time to start compiling your projects with DIP1000, too!

Congratulations to the whole team behind it.

On 5/14/2019 11:49 PM, Dukc wrote:
> About -DIP1000, I sure want to use it. But is there currently any practical way to learn it's usage without researching compiler source code?

This is a good start:

http://dconf.org/2017/talks/bright.html

On 5/15/2019 12:21 AM, Dukc wrote:
> Could be worth a try even without docs, but in the long run we definitely need some explaining.

True, but I've tried fairly hard with the error messages. Please post your experiences with them.

Also, there shouldn't be any caveats with using it. If it passes the compiler, it should be good to go. (Much like const and pure.)

In general, if you find the error messages baffling, try reducing your code to a simpler example. This usually makes the problem clearer. dustmite is a great tool to help with that.