On Tuesday, 27 August 2019 at 17:11:33 UTC, Mike Franklin wrote:
If you look at the vibe.d compile-time graph, you'll see
there's a 2.5s increase around Mid-2014.
Sorry, that should be Mid-2015.
On Tue, Aug 27, 2019 at 12:25 PM Ali Çehreli via
Digitalmars-d-announce wrote:
>
> I will be presenting a comparison of D and C++. RSVP so that we know how
> much food to order:
>
>https://www.meetup.com/ACCU-Bay-Area/events/263679081/
>
> It will not be streamed live but some people want to
I will be presenting a comparison of D and C++. RSVP so that we know how
much food to order:
https://www.meetup.com/ACCU-Bay-Area/events/263679081/
It will not be streamed live but some people want to record it; so, it
may appear on YouTube soon.
As always, I have way too many slides. :)
On Monday, 26 August 2019 at 18:51:54 UTC, Vladimir Panteleev
wrote:
On Sunday, 25 August 2019 at 13:38:24 UTC, Mike Parker wrote:
The Symmetry Autumn of Code 2019 application selection process
has come to an end. This year, we've got five projects instead
of three. Congratulations to everyone
On Tuesday, 27 August 2019 at 14:42:28 UTC, Vladimir Panteleev
wrote:
On Monday, 26 August 2019 at 18:51:54 UTC, Vladimir Panteleev
wrote:
On Sunday, 25 August 2019 at 13:38:24 UTC, Mike Parker wrote:
The Symmetry Autumn of Code 2019 application selection
process has come to an end. This year,
On Tuesday, 27 August 2019 at 12:58:20 UTC, Vladimir Panteleev
wrote:
It will eventually zero in to commit-level accuracy after it's
been running for a while. I cleared the database as the last
time it was running, it was on another CPU, so the timings are
going to be different. (Still need
On Monday, 26 August 2019 at 18:51:54 UTC, Vladimir Panteleev
wrote:
On Sunday, 25 August 2019 at 13:38:24 UTC, Mike Parker wrote:
The Symmetry Autumn of Code 2019 application selection process
has come to an end. This year, we've got five projects instead
of three. Congratulations to everyone
On Tuesday, 27 August 2019 at 09:08:58 UTC, Mike Franklin wrote:
It's great to see this back up and running. The compile-time
data is quite interesting. Is there any way to identify a
particular offending commit. The commits identified in the data
points on the chart don't seem to be
Is this supports only in dub-1.17.0-beta.2 and it's not include
to ldc2-1.17.0?
It feature only in dub-master by now
But it's cool works) Thanks!
On Sunday, 25 August 2019 at 21:16:22 UTC, kinke wrote:
The resulting cctest.exe (incl. 2 DLLs) can be copied to a
Win64 box and then runs fine, as long as a Visual C++ runtime ≥
2015 is installed. Tested on a Linux host, but should work on
any host.
Is this supports only in
On Monday, 26 August 2019 at 18:51:54 UTC, Vladimir Panteleev
wrote:
Here's the original blog post:
https://blog.thecybershadow.net/2015/05/05/is-d-slim-yet/
I'll give it a kick and get it back online if there is
interest. Seems wasteful to reimplement it from scratch, though.
It's great
11 matches
Mail list logo
