On Wednesday, 20 November 2019 at 13:37:39 UTC, Jacob Carlborg
wrote:
On Wednesday, 20 November 2019 at 11:40:19 UTC, Robert Schadek
wrote:
Here is disagree, to a degree I consider comments a code smell.
If I have to write them, I failed to convey the information
needed to understand the code
I assume you don't mean the documentation for std.array
specifically,
but the act of having documentation of the module.
Then, yes I do think documentation should not be needed.
I think it would be far better if I only needed the signatures of
the functions and the members of the structs to use
On Wednesday, 20 November 2019 at 11:40:19 UTC, Robert Schadek
wrote:
Here is disagree, to a degree I consider comments a code smell.
If I have to write them, I failed to convey the information
needed to understand the code in the code.
You think this is a code smell:
https://dlang.org/phobo
On Tuesday, 19 November 2019 at 17:13:49 UTC, Nick Sabalausky
(Abscissa) wrote:
On 11/19/19 11:30 AM, Steven Schveighoffer wrote:
And I would complain that the fact json exists as a file
format already screws up dub add -- using dub add removes ALL
comments in an SDL file, and rewrites the fi
On Tuesday, 19 November 2019 at 16:30:26 UTC, Steven
Schveighoffer wrote:
And I would complain that the fact json exists as a file format
already screws up dub add -- using dub add removes ALL comments
in an SDL file, and rewrites the file in the order it sees fit.
result: I don't use dub add
On Monday, 18 November 2019 at 12:59:25 UTC, Joseph Rushton
Wakeling wrote:
Cool :-) Since I have also been experiencing a fair bit of
production-use DUB pain in the last year, I really appreciate
your taking action on this.
A few things that would be good to understand up front:
* what
On Wednesday, 20 November 2019 at 08:32:37 UTC, Walter Bright
wrote:
Title
A Unifying Abstraction for Async in C++
[...]
Come join us, it'll be fun!
Will this talk be recorded?
On 11/20/2019 1:06 AM, Les De Ridder wrote:
Will this talk be recorded?
They usually are, but sometimes something goes wrong with the camera.
Title
A Unifying Abstraction for Async in C++
Abstract
Async in C++ is in a sad state. The standard tools — promises, futures, threads,
locks, and std::async — are either inefficient, broken, or both. Even worse,
there is no standard way to say _where_ work should happen. Parallel algorithms,
