On 04/11/2017 02:22 AM, qznc wrote:
On Tuesday, 11 April 2017 at 06:08:16 UTC, Ali Çehreli wrote:
I will be presenting D as a time-saving tool at C++Now:
http://cppnow.org/
Looks like C++Now has two keynotes. One keynote on D and one keynote on
Rust. Maybe they should change their name. ;)
On 04/11/2017 11:01 PM, Szabo Bogdan wrote:
should.not.throwAnyException({
throw new Exception("test");
});
what do you mean, they are not documented? there is a md file fith some
examples here:
https://github.com/gedaiu/fluent-asserts/blob/v0.3.0/api/exceptions.md
What do you
On Monday, 10 April 2017 at 20:53:00 UTC, Joseph Rushton Wakeling
wrote:
You didn't get my messages on slack about the backend license,
then :-(
I'd assumed that was the fastest way to reach you -- I should
have filed an issue sooner.
Usually works, but had too much to do to handle another
On Tuesday, 11 April 2017 at 10:40:53 UTC, qznc wrote:
On Sunday, 9 April 2017 at 13:30:54 UTC, Szabo Bogdan wrote:
Hi!
I just made an update to my fluent assert library. This is a
library that allows you to write asserts in a BDD style.
Right now, it contains only asserts that I needed in
On Monday, 10 April 2017 at 08:11:37 UTC, Atila Neves wrote:
On Sunday, 9 April 2017 at 13:59:14 UTC, Andrei Alexandrescu
wrote:
Great. Can RefCounted itself be shared? I learned this is
important for composition, i.e. you want to make a RefCounted
a field in another object that is itself
On Wednesday, 12 April 2017 at 05:51:20 UTC, Ali Çehreli wrote:
On 04/10/2017 06:07 AM, Mike Parker wrote:
Stefan has been diligently keeping us all updated on NewCTFE
here in the
forums. Now, he's gone to the blog to say something to tell
the world
about it.
The blog:
DIP 1006 is titled "Providing more selective control over
contracts". This announcement kicks off the first round of
preliminary reviews. The review thread can be found in the
General forum at:
http://forum.dlang.org/post/rsafosvkhxddkxpta...@forum.dlang.org
On 04/10/2017 04:48 PM, Sönke Ludwig wrote:
The 0.7.x branch will continue to be maintained for a short
while, but only bug fixes will be included from now on. Applications
should switch to the 0.8.x branch as soon as possible.
If a library depends on vibe, but wants to allow its users to use
