On 5/31/17 7:28 PM, Nicholas Wilson wrote:
On Wednesday, 31 May 2017 at 22:15:33 UTC, Wulfklaue wrote:
On Wednesday, 31 May 2017 at 12:28:47 UTC, Nicholas Wilson wrote:
Perhaps there will be scope for renaming if/when this also includes
graphics when either OpenCL is merged into the Vulkan API
On 5/31/17 6:03 PM, Jonathan M Davis via Digitalmars-d-announce wrote:
On Wednesday, May 31, 2017 18:55:14 bachmeier via Digitalmars-d-announce
wrote:
On Wednesday, 31 May 2017 at 12:28:47 UTC, Nicholas Wilson wrote:
But can we please reduce the bike shedding
Marketing is only bike shedding
On 06/03/2017 11:08 AM, Andrei Alexandrescu wrote:
On 6/2/17 10:17 AM, Mike Parker wrote:
Congratulations are in order for Jared Hanson. Walter and Andrei have
approved his proposal to remove body as a keyword. I've added a
summary of their decision to the end of the DIP for anyone who cares
On 6/2/17 10:17 AM, Mike Parker wrote:
Congratulations are in order for Jared Hanson. Walter and Andrei have
approved his proposal to remove body as a keyword. I've added a summary
of their decision to the end of the DIP for anyone who cares to read it.
In short:
* body temporarily becomes a
On 5/30/17 3:23 PM, Jack Stouffer wrote:
On Tuesday, 30 May 2017 at 18:06:56 UTC, Walter Bright wrote:
I fear the conversation will go like this, like it has for me:
N: DCompute
W: What's DCompute?
N: Enables GPU programming with D
W: Cool!
instead of:
N: D-GPU
W: Cool! I can use D to
On 6/8/17 5:03 PM, Wulfklaue wrote:
On Thursday, 8 June 2017 at 20:38:33 UTC, Ali Çehreli wrote:
That link doesn't work for me. Besides, I've heard that it's better
not to click through a link as HN either rates it lower or flags it as
spam.
Not sure though, I'm just contributing to cargo
On 5/7/17 10:59 AM, Brian Schott wrote:
I moved DCD, D-Scanner, dfmt, and other D tool projects to the
dlang-community organization on Github:
https://github.com/dlang-community
This should make things more convenient if I get hit by a bus, decide
that Malbolge* is the one true programming
Zoom in on the screen for a nice surprise! http://imgur.com/a/qjI4l --
Andrei
https://erdani.com/dconf2017-slides.pdf -- Andrei
Hello everyone, it is my pleasure to announce that Alexandru Jercaianu,
a starting MSc student at University "Politehnica" Bucharest, is
recipient of our scholarship.
Alex is up and running working on his bootcamp tasks. Currently he is
attempting unsuccessfully to post in our general group
With the Feb 25 deadline looming, allow me to holler to everyone who has
worked on great things in the D language through the past year: please
make a DConf 2018 submission!
By all measures there's been significant pick up in contributions to the
D language during the recent months, and it
On 12/20/17 8:57 AM, Mike Parker wrote:
Many thanks to Rainer for his insightful new article for the D Blog
outlining the new name mangling algorithm. He talks about the old
implementation and its limitations before going into the details of the
new one. It's a topic I had never considered
Amazon has a nonprofit arm:
https://smile.amazon.com
Go there and choose The D Language Foundation as your charity of choice,
then shop normally through smile.amazon.com. A fraction of your
expenditure will go to the Foundation.
Thanks,
Andrei
Hello, the vision document of the Founation for the first six months of
2018 is here:
https://wiki.dlang.org/Vision/2018H1
In addition to the expected items, we have a new top-level priority -
locking down the language definition. This is in recognition of the fact
that we need a precise
On 2/25/18 8:03 PM, aliak wrote:
Alo,
Just finished up a first take on an optional type for D. It's
essentially a mix of Nullable and std.range.only, but with a lot more
bells and whistles. I would love to hear any feedback on code, or
features, or bad design or potential for better designs
On 2/28/18 12:54 PM, Andrei Alexandrescu wrote:
On 2/25/18 8:03 PM, aliak wrote:
Alo,
Just finished up a first take on an optional type for D. It's
essentially a mix of Nullable and std.range.only, but with a lot more
bells and whistles. I would love to hear any feedback on code
Of possible interest:
https://www.technotification.com/2019/01/most-underrated-programming-languages.html
https://youtube.com/watch?v=tcyb1lpEHm0
If nothing else please watch the opening story, it's true and quite
funny :o).
Now as to the talk, as you could imagine, it touches on another language
as well...
Andrei
On 1/12/19 7:21 PM, Bastiaan Veelo wrote:
On Saturday, 12 January 2019 at 15:51:03 UTC, Andrei Alexandrescu wrote:
https://youtube.com/watch?v=tcyb1lpEHm0
If nothing else please watch the opening story, it's true and quite
funny :o).
Now as to the talk, as you could imagine, it touches
On 1/24/19 3:01 PM, kinke wrote:
On Thursday, 24 January 2019 at 09:49:14 UTC, Manu wrote:
We discussed and concluded that one mechanism to mitigate this issue
was already readily available, and it's just that 'out' gains a much
greater sense of identity (which is actually a positive
On 1/24/19 2:18 AM, Mike Parker wrote:
Walter and Andrei have declined to accept DIP 1016, "ref T accepts
r-values", on the grounds that it has two fundamental flaws that would
open holes in the language. They are not opposed to the feature in
principle and suggested that a proposal that
On 2/25/19 1:39 PM, Jacob Carlborg wrote:
On 2019-02-25 17:31, Andrei Alexandrescu wrote:
The proposers (Razvan and myself) and Walter (the reviewer) do not
know how to make DIP 1018 better.
That shouldn't justify accepting a DIP that might contain problems.
Definitely.
But of course
On 2/25/19 3:23 PM, Jacob Carlborg wrote:
On 2019-02-25 20:24, Mike Parker wrote:
From the process document:
“the DIP Manager or the Language Maintainers may allow for exceptions
which waive requirements or responsibilities at their discretion.”
Having it documented doesn't make it less
On 2/25/19 3:41 PM, Paolo Invernizzi wrote:
On Monday, 25 February 2019 at 20:23:58 UTC, Andrei Alexandrescu wrote:
On 2/25/19 3:23 PM, Jacob Carlborg wrote:
On 2019-02-25 20:24, Mike Parker wrote:
From the process document:
“the DIP Manager or the Language Maintainers may allow
On 2/25/19 2:24 PM, Mike Parker wrote:
On Monday, 25 February 2019 at 18:51:17 UTC, Jacob Carlborg wrote:
On 2019-02-24 11:46, Mike Parker wrote:
Walter and Andrei have requested the Final Review round be dropped
for DIP 1018, "The Copy Constructor", and have given it their formal
approval.
On 2/25/19 2:41 PM, bachmeier wrote:
On Monday, 25 February 2019 at 19:24:55 UTC, Mike Parker wrote:
From the process document:
“the DIP Manager or the Language Maintainers may allow for exceptions
which waive requirements or responsibilities at their discretion.”
If you were to write a
On 2/25/19 9:26 PM, Manu wrote:
On Mon, Feb 25, 2019 at 12:20 PM Andrei Alexandrescu via
Digitalmars-d-announce wrote:
On 2/25/19 2:41 PM, bachmeier wrote:
On Monday, 25 February 2019 at 19:24:55 UTC, Mike Parker wrote:
From the process document:
“the DIP Manager or the Language
On 2/25/19 7:23 PM, Nicholas Wilson wrote:
There are similarities and differences between our DIP process and
paper submission reviews at conferences and journals everywhere; one
key similarity is that the submitters are on hook for providing
convincing submissions, whereas reviewers are not
On 2/25/19 6:09 PM, Olivier FAURE wrote:
Yes, this DIP was fast-tracked. Yes, this can feel unfair. And yet, it
makes sense that it was fast-tracked, because it fits a priority of the
project owners (C++ interoperability + reference counting) and project
owners are allowed to have priorities.
On 2/24/19 4:02 PM, Manu wrote:
On Sun, Feb 24, 2019 at 2:50 AM Mike Parker via Digitalmars-d-announce
wrote:
Walter and Andrei have requested the Final Review round be
dropped for DIP 1018, "The Copy Constructor", and have given it
their formal approval. They consider copy constructors a
On 02/25/2019 03:41 PM, Paolo Invernizzi wrote:
On Monday, 25 February 2019 at 20:23:58 UTC, Andrei Alexandrescu wrote:
On 2/25/19 3:23 PM, Jacob Carlborg wrote:
On 2019-02-25 20:24, Mike Parker wrote:
From the process document:
“the DIP Manager or the Language Maintainers may allow
On 2/25/19 1:06 AM, Nicholas Wilson wrote:
On Monday, 25 February 2019 at 02:56:13 UTC, Walter Bright wrote:
Your DIP, and nobody else is going to do it, so it falls to me.
It will be reviewed at Dconf, please make sure you have an _accurate_
summary of your criticisms of the DIP ready for
On 2/25/19 10:45 AM, Atila Neves wrote:
The *only* problem I have with const in D is that const values can't be
copied, which is silly. I'd expect DIP1018 to fix that.
Affirmative. It was tricky.
On 2/26/19 5:34 PM, Seb wrote:
Hi all,
I have some very exciting news to share.
The D Language Language got accepted as a Google Summer of Code
organization!
A few of us were waiting for permission to announce all day :o).
Congratulations to Mike, Seb, and all others who made our proposal
On 1/29/19 10:57 AM, Adam D. Ruppe wrote:
On Tuesday, 29 January 2019 at 15:48:23 UTC, Andrei Alexandrescu wrote:
On 1/29/19 10:44 AM, Nicholas Wilson wrote:
if (auto val = expr(); val) { ... },
Since we don't have these constructs, lowering would need to explain
what happens here
On 1/29/19 10:44 AM, Nicholas Wilson wrote:
On Tuesday, 29 January 2019 at 11:52:40 UTC, Andrei Alexandrescu wrote:
While writing this example:
int[] a = cast(int[]) alloc.allocate(100 * int.sizeof);
if (alloc.reallocate(a, 200 * int.sizeof))
{
assert(a.length == 200);
}
=>
On 1/28/19 1:00 PM, Andrei Alexandrescu wrote:
On 1/24/19 3:01 PM, kinke wrote:
On Thursday, 24 January 2019 at 09:49:14 UTC, Manu wrote:
We discussed and concluded that one mechanism to mitigate this issue
was already readily available, and it's just that 'out' gains a much
greater sense
On 1/28/19 5:23 PM, Steven Schveighoffer wrote:
I already see this kind of bug all the time with alias this.
Can you please post more detail? It may be of relevance to future work.
On 1/30/19 3:34 AM, Kagamin wrote:
On Tuesday, 29 January 2019 at 11:52:40 UTC, Andrei Alexandrescu wrote:
Where should the temporary go?
Doesn't D already specify allocation and lifetime of temporaries? AIU
the DIP doesn't invent the notion of a temporary.
My bad, I overloaded the term
On 1/30/19 1:29 PM, Manu wrote:
On Wed, Jan 30, 2019 at 9:20 AM Neia Neutuladh via
Digitalmars-d-announce wrote:
On Wed, 30 Jan 2019 09:15:36 -0800, Manu wrote:
Why are you so stuck on this case? The DIP is about accepting rvalues,
not lvalues...
Calling with 'p', an lvalue, is not subject
On 1/31/19 11:38 AM, Steven Schveighoffer wrote:
On 1/31/19 11:04 AM, Olivier FAURE wrote:
On Thursday, 31 January 2019 at 02:10:05 UTC, Manu wrote:
I still can't see a truck-sized hole.
I don't know if it's truck-sized, but here's another corner case:
int doubleMyValue(ref int x) {
On 1/31/19 4:42 PM, Olivier FAURE wrote:
On Thursday, 31 January 2019 at 16:38:42 UTC, Steven Schveighoffer wrote:
Yeah, that's already a thing that ref in D doesn't protect against:
It took me a while to understand what the compiler was doing.
This really feels like something that shouldn't
On 1/30/19 10:12 PM, Manu wrote:
On Wed, Jan 30, 2019 at 7:05 PM Nicholas Wilson via
Digitalmars-d-announce wrote:
On Thursday, 31 January 2019 at 02:10:05 UTC, Manu wrote:
On Wed, Jan 30, 2019 at 1:05 PM Andrei Alexandrescu via
fun(my_short); // implicit type conversions (ie, short->
On 1/30/19 9:10 PM, Manu wrote:
* Its own author seems to not have an understanding of what the DIP
proposes.
More classy comments. I can't get enough of the way you belittle people.
You're right. I have deleted this post a few seconds after having sent
it on account of that remark, but
On 1/30/19 10:05 PM, Manu wrote:
On Wed, Jan 30, 2019 at 6:40 PM Nicholas Wilson via
Digitalmars-d-announce wrote:
On Wednesday, 30 January 2019 at 18:29:37 UTC, Manu wrote:
On Wed, Jan 30, 2019 at 9:20 AM Neia Neutuladh via
Digitalmars-d-announce
wrote:
The result of a CastExpression is
On 1/29/19 1:01 AM, Manu wrote:
This DIP is about passing rvalues to ref... so the issue you describe
passing lvalues to ref does not apply here.
There is no suggestion to change lvalue rules anywhere in this DIP.
The problem is with rvalues resulting as temporaries from lvalues. As in:
void
On 1/29/19 6:45 AM, Andrei Alexandrescu wrote:
It is truly remarkable that DIP 1016 provides not only a solution to the
problem, but almost neglects to mention it.
Meant "...not only no solution..."
On 1/29/19 3:35 AM, Manu wrote:
1. All of this is more useful criticism than the official and final
criticism affixed to the rejection, which when revised to remove the
incorrect criticisms, is basically left with the text "The Language
Maintainers found other issues with the proposal, most of
On 1/29/19 6:38 AM, Nicholas Wilson wrote:
On Tuesday, 29 January 2019 at 08:35:11 UTC, Manu wrote:
4. "Under DIP 1016, a call with any T[] will silently "succeed" by
converting the slice to void[]" <-- Do you mean "... with any T[]
rvalue ..."? What would be the aim of that call? Can you
While writing this example:
int[] a = cast(int[]) alloc.allocate(100 * int.sizeof);
if (alloc.reallocate(a, 200 * int.sizeof))
{
assert(a.length == 200);
}
=>
int[] a = cast(int[]) alloc.allocate(100 * int.sizeof);
void[] __temp0 = a;
if (alloc.reallocate(__temp0, 200 * int.sizeof)
{
Just checked, it works:
https://youtu.be/Vj6jNAlv03o
On 5/12/19 11:27 AM, Isaac S. wrote:
This is the crux of the argument: *How* does making bool an integer add
to the language?
The crux of the argument is there was a D Improvement Proposal on a
small language change, and it was rejected.
Rejected D Improvement Proposals on small matters
On 5/12/19 11:46 PM, H. S. Teoh wrote:
On Sun, May 12, 2019 at 01:20:16PM +, Mike Franklin via
Digitalmars-d-announce wrote:
[...]
If anyone's looking for a challenge, I welcome them to propose a new
`Bool` type (note the capital B) for inclusion in my new library.
[...]
As long as &&
On 5/14/19 8:47 PM, Mike Franklin wrote:
On Tuesday, 14 May 2019 at 15:40:19 UTC, Kagamin wrote:
On Sunday, 12 May 2019 at 06:27:21 UTC, Nick Sabalausky (Abscissa) wrote:
All this effort strongly implies that there's no such thing as a
satisfactory bool type *in languages which conflate
On 5/14/19 2:00 AM, Mike Franklin wrote:
On Wednesday, 15 May 2019 at 00:23:44 UTC, Andrei Alexandrescu wrote:
There are many clowny things in D, of which bool is at best somewhere
beyond the radar. I suggest investing time * expertise in the larger
ones.
Once again, I disagree with what
On 5/12/19 1:34 PM, Nicholas Wilson wrote:
However in this case the community consensus is that the chain of
reasoning you have used to arrive at your decision is wrong.
It's a simple enough matter to be understood, and reasonable to assume
Walter is not missing any important facts or
Google Alerts just found these slides:
https://speakerdeck.com/shigekikarita/grain-d-language-for-deep-learning
Does anyone have more information about this?
On 10/6/19 3:09 AM, Joseph Rushton Wakeling wrote:
You misunderstand what I mean by "battle-testing". Clearly designs
should go through a high level of testing and usage before they go
anywhere near the standard library. But the very fact of being placed in
the standard library exposes them to
On 10/5/19 7:58 AM, Seb wrote:
On Saturday, 5 October 2019 at 06:40:35 UTC, Arun Chandrasekaran wrote:
On Saturday, 5 October 2019 at 02:59:58 UTC, Paul Backus wrote:
I was curious how C++17's std::variant compared to the options we
have in D, like Algebraic and SumType, so I did a simple
Walter, Mike, and I are happy to announce that our paper submission
"Origins of the D Programming Language" has been accepted at the HOPL IV
(History of Programming Languages) conference.
https://hopl4.sigplan.org/track/hopl-4-papers
Getting a HOPL paper in is quite difficult, and an
On 5/14/20 11:57 AM, jmh530 wrote:
On Thursday, 14 May 2020 at 13:40:24 UTC, Andrei Alexandrescu wrote:
[snip]
Really interesting. Thanks for sharing.
I have recently been spending some spare time learning more about D's
topN and pivotPartition implementation, which led me to your paper
On 5/14/20 9:26 AM, Mike Parker wrote:
After reading a paper that grabbed his curiosity and wouldn't let go,
Andrei set out to determine if Lomuto partitioning should still be
considered inferior to Hoare for quicksort on modern hardware. This blog
post details his results.
Blog:
On 5/14/20 9:26 AM, Mike Parker wrote:
After reading a paper that grabbed his curiosity and wouldn't let go,
Andrei set out to determine if Lomuto partitioning should still be
considered inferior to Hoare for quicksort on modern hardware. This blog
post details his results.
Blog:
On 5/21/20 7:49 PM, Bruce Carneal wrote:
On Thursday, 21 May 2020 at 16:32:32 UTC, Adam D. Ruppe wrote:
On Thursday, 21 May 2020 at 16:14:02 UTC, Seb wrote:
Why we can't we have a technical board where the community can vote
in experts and potentially companies could even buy a seat for $$$
On 5/23/20 6:49 PM, ag0aep6g wrote:
On 23.05.20 17:07, Andrei Alexandrescu wrote:
A fork does exist. As expected it went nowhere.
https://bitbucket.org/larsivi/amber/wiki/Home. There is a paradox
about forking the language - anyone good enough to lead a successful
fork would also be wise
On 10/1/20 5:08 PM, Meta wrote:
On Thursday, 1 October 2020 at 20:37:04 UTC, kinke wrote:
On Thursday, 1 October 2020 at 18:29:14 UTC, Meta wrote:
If W or A did approve it and I just wasn't aware, then I apologize
and retract my objection.
On 9/12/20 4:56 PM, Steven Schveighoffer wrote:
I wanted to once again give people a good notice for the next upcoming
beerconf, happening September 26th and 27th. As usual, bring your
favorite beverage (non alcoholic if you prefer), and bring your D topics
to discuss with the crew. 3 months
On 5/27/20 6:03 AM, Walter Bright wrote:
On 5/26/2020 5:20 AM, Johannes T wrote:
On Tuesday, 26 May 2020 at 03:37:29 UTC, Walter Bright wrote:
[..]
Thank you very much for your patience with all the negative feedback.
I get your decision to not annotate extern C with @system by default.
On 5/27/20 6:22 AM, Walter Bright wrote:
On 5/27/2020 3:06 AM, rikki cattermole wrote:
Open to everybody and it can be recorded by Twitch.
I've done the video conferencing many times over the decades. I just
don't find it to be productive. Maybe it's some defect in me.
They usually go
On 5/27/20 9:42 AM, Andrej Mitrovic wrote:
On Wednesday, 27 May 2020 at 09:50:50 UTC, Walter Bright wrote:
Un-annotated C declarations should be a red flag to any competent QA
team. Recognizing a false @trusted is a whole lot harder.
Is the actual problem those `@trusted:` declarations at the
The DIP is trying to accomplish (copied from its Rationale):
A. Costs of unsafe code have become ever more apparent and expensive,
and @safe has grown more capable. Users expect safety to be opt-out, not
opt-in.
B. Most code should be naturally safe, and system code should be
relatively
On 5/29/20 12:53 AM, Walter Bright wrote:
The subject says it all.
If you care about memory safety, I recommending adding `safe:` as the
first line in all your project modules, and annotate individual
functions otherwise as necessary. For modules with C declarations, do as
you think best.
https://www.phoronix.com/scan.php?page=news_item=Alpine-Linux-3.12-Released
On 5/30/20 7:39 AM, Nick Treleaven wrote:
On Friday, 29 May 2020 at 21:18:13 UTC, Walter Bright wrote:
On 5/29/2020 2:07 AM, Timon Gehr wrote:
It would be great if `@safe:` did not affect declarations that would
otherwise infer annotations.
The idea is the simple, general rule that:
On 5/26/20 12:31 PM, Bruce Carneal wrote:
Currently a machine checked @safe function calling an unannotated extern
C routine will error out during compilation. This is great as the C
routine was not machine checked, and generally can not be checked. Post
1028, IIUC, the compilation will go
On 5/27/20 1:49 AM, Walter Bright wrote:
On 5/26/2020 9:31 AM, Bruce Carneal wrote:
Currently a machine checked @safe function calling an unannotated
extern C routine will error out during compilation. This is great as
the C routine was not machine checked, and generally can not be
checked.
On 7/7/20 8:04 AM, Steven Schveighoffer wrote:
On 7/7/20 7:13 AM, 9il wrote:
On Tuesday, 7 July 2020 at 07:49:02 UTC, Walter Bright wrote:
On 7/5/2020 5:46 AM, Joseph Rushton Wakeling wrote:
On Sunday, 5 July 2020 at 11:07:55 UTC, 9il wrote:
There is no risk for DMD and DFL to depend on a
On 8/4/20 9:49 AM, Andrei Alexandrescu wrote:
On 8/4/20 4:19 AM, Iain Buclaw wrote:
On 04/08/2020 03:14, Andrei Alexandrescu wrote:
Interesting, thanks!
Did a quick benchmark for n in `seq 1 10` ./lomuto.exe ${n}00...
[snip]
Looks good, so committing patch. :-)
Awesome, thanks
On 8/4/20 4:19 AM, Iain Buclaw wrote:
On 04/08/2020 03:14, Andrei Alexandrescu wrote:
Interesting, thanks!
Did a quick benchmark for n in `seq 1 10` ./lomuto.exe ${n}00...
[snip]
Looks good, so committing patch. :-)
Awesome, thanks! That does solve a puzzler I had while benchmarking
On 6/23/20 10:31 AM, Meta wrote:
On Tuesday, 23 June 2020 at 13:45:56 UTC, user1234 wrote:
On Tuesday, 23 June 2020 at 12:00:30 UTC, Mike Parker wrote:
On Tuesday, 23 June 2020 at 12:00:06 UTC, Mike Parker wrote:
Symmetry Autumn of Code 2020 is on! My latest news post on the D
Blog talks
On 6/26/20 1:02 PM, Avrina wrote:
On Friday, 26 June 2020 at 13:35:20 UTC, Andrei Alexandrescu wrote:
On 6/26/20 9:03 AM, Avrina wrote:
On Friday, 26 June 2020 at 05:37:13 UTC, Arun Chandrasekaran wrote:
On Thursday, 25 June 2020 at 11:55:14 UTC, Mike Parker wrote:
I've also submitted
How to answer "why will yours succeed, when X, Y, and Z have failed?"
https://www.youtube.com/watch?v=wIHfaH9Kffs
Very insightful talk.
On 6/17/20 7:19 AM, Atila Neves wrote:
On Wednesday, 17 June 2020 at 10:43:35 UTC, Stanislav Blinov wrote:
On Saturday, 13 June 2020 at 15:11:49 UTC, Atila Neves wrote:
Tardy lets users have their cake and eat it too by not making them
have to use classes for runtime polymorphism.
I've got
On 6/26/20 9:03 AM, Avrina wrote:
On Friday, 26 June 2020 at 05:37:13 UTC, Arun Chandrasekaran wrote:
On Thursday, 25 June 2020 at 11:55:14 UTC, Mike Parker wrote:
I've also submitted it to HN (please use the search box):
https://news.ycombinator.com/newest
This is a very interesting post.
On 6/24/20 5:01 PM, Martin Nowak wrote:
Glad to announce the first beta for the 2.093.0 release, ♥ to the 53
contributors.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.093.0.html
As usual please report any bugs at
https://issues.dlang.org
-Martin
Thanks! Would be
https://github.com/ZigaSajovic/optimizing-the-memory-layout-of-std-tuple
Would be interesting to adapt it for std.tuple.
On 6/13/20 2:39 PM, Paul Backus wrote:
On Saturday, 13 June 2020 at 15:11:49 UTC, Atila Neves wrote:
https://code.dlang.org/packages/tardy
https://github.com/atilaneves/tardy
Cool stuff!
What's the reasoning behind implementing your own vtables instead of
using D's built-in object system?
PLDI (Programming Language Design and Implementation) is a top academic
conference. This year PLDI will be held online and registration is free.
This is an amazing treat.
https://conf.researchr.org/home/pldi-2020
Workshops and tutorials (also free) are of potential interest. These
caught my
On 6/13/20 11:55 PM, Avrina wrote:
On Sunday, 14 June 2020 at 03:08:48 UTC, Andrei Alexandrescu wrote:
On 6/13/20 7:30 PM, Timon Gehr wrote:
Another question is if automatic packing is worth making the layout
harder to predict.
I think so. Size does matter.
If you are talking about
On 6/13/20 7:30 PM, Timon Gehr wrote:
Another question is if automatic packing is worth making the layout
harder to predict.
I think so. Size does matter.
On 6/14/20 12:26 PM, Avrina wrote:
On Sunday, 14 June 2020 at 03:57:40 UTC, Andrei Alexandrescu wrote:
On 6/13/20 11:55 PM, Avrina wrote:
On Sunday, 14 June 2020 at 03:08:48 UTC, Andrei Alexandrescu wrote:
On 6/13/20 7:30 PM, Timon Gehr wrote:
Another question is if automatic packing is worth
On 6/14/20 2:25 PM, Paul Backus wrote:
On Sunday, 14 June 2020 at 16:26:17 UTC, Avrina wrote:
The situation also applies to the only tuple implementation in D. If
you are proposing a new type with emphasis on reducing the footprint
of the tuple then I don't see a problem with that. Changing
On 6/14/20 3:36 PM, Timon Gehr wrote:
On 14.06.20 20:25, Paul Backus wrote:
On Sunday, 14 June 2020 at 16:26:17 UTC, Avrina wrote:
The situation also applies to the only tuple implementation in D. If
you are proposing a new type with emphasis on reducing the footprint
of the tuple then I
On 6/14/20 4:22 PM, Timon Gehr wrote:
On 04.06.20 14:46, Andrei Alexandrescu wrote:
PLDI (Programming Language Design and Implementation) is a top
academic conference. This year PLDI will be held online and
registration is free. This is an amazing treat.
https://conf.researchr.org/home/pldi
On 2021-10-13 7:27, Andrey Zherikov wrote:
Hi everyone,
I'm happy to announce that I've published a CLI argument parsing library
- [argparse](https://code.dlang.org/packages/argparse). It's been around
for some time already so please take a look and provide your feedback if
you haven't done
1301 - 1395 of 1395 matches
Mail list logo
