On Tuesday, 23 July 2019 at 22:01:56 UTC, Sebastiaan Koppe wrote:
So in a nutshell, a variable with the unique qualifier ensures
that there are no other references to that data during the
lifetime of said variable? In other words, you can only take 1
addressOf/ref at a time?
Does it prevent
On Tuesday, 23 July 2019 at 19:15:44 UTC, Olivier FAURE wrote:
That's as good a time as any to plug my own proposal draft:
https://gist.github.com/PoignardAzur/9896ddb17b9f6d6f3d0fa5e6fe1a7088
Any thoughts?
So in a nutshell, a variable with the unique qualifier ensures
that there are no
On Tuesday, 23 July 2019 at 14:18:27 UTC, Timon Gehr wrote:
I think tying ownership/borrowing semantics to pointers instead
of structs makes no sense; it's not necessary and it's not
sufficient. Your use case illustrates why it is not sufficient.
That's as good a time as any to plug my own
On 23.07.19 10:20, Sebastiaan Koppe wrote:
On Tuesday, 23 July 2019 at 04:02:50 UTC, Timon Gehr wrote:
On 21.07.19 02:17, Walter Bright wrote:
On 7/20/2019 3:39 PM, Sebastiaan Koppe wrote:
Do you mean to keep track of ownership/borrowedness manually?
No, that's what the
On Tuesday, 23 July 2019 at 11:28:35 UTC, Francesco Mecca wrote:
On Monday, 22 July 2019 at 15:58:08 UTC, a11e99z wrote:
On Monday, 22 July 2019 at 14:03:15 UTC, Mike Parker wrote:
Francesco Mecca ha written an experience report for the D
thanks for answers
On Monday, 22 July 2019 at 15:58:08 UTC, a11e99z wrote:
On Monday, 22 July 2019 at 14:03:15 UTC, Mike Parker wrote:
Francesco Mecca ha written an experience report for the D Blog
about his SAOC 2018 project, porting Leandro Lucarella's old
GC from D1 to D2.
The blog:
On Tuesday, 16 July 2019 at 20:18:30 UTC, John Colvin wrote:
On Tuesday, 16 July 2019 at 18:18:50 UTC, Atila Neves wrote:
On Tuesday, 16 July 2019 at 00:10:19 UTC, Aliak wrote:
On Monday, 15 July 2019 at 21:20:16 UTC, Atila Neves wrote:
On Monday, 15 July 2019 at 11:13:10 UTC, aliak wrote:
On 23/07/2019 9:50 PM, Francesco Mecca wrote:
On Monday, 22 July 2019 at 16:52:08 UTC, rikki cattermole wrote:
I may have another try at it, if somebody can give me pointers on
where the actual reading occurs in the GC. Because it has left me a
bit stumped.
Come talk in the IRC channel. I am
On Monday, 22 July 2019 at 16:52:08 UTC, rikki cattermole wrote:
I may have another try at it, if somebody can give me pointers
on where the actual reading occurs in the GC. Because it has
left me a bit stumped.
Come talk in the IRC channel. I am there and people are super
helpful.
On Monday, 22 July 2019 at 20:57:19 UTC, Meta wrote:
On Monday, 22 July 2019 at 14:03:15 UTC, Mike Parker wrote:
> [...]
A pull request to the D runtime was my final milestone. I was
ready at the beginning of February, but I started to
procrastinate. I’d had no previous communication with
On Tuesday, 23 July 2019 at 04:02:50 UTC, Timon Gehr wrote:
On 21.07.19 02:17, Walter Bright wrote:
On 7/20/2019 3:39 PM, Sebastiaan Koppe wrote:
Do you mean to keep track of ownership/borrowedness manually?
No, that's what the copyctor/opAssign/dtor semantics so.
This is not true.
I
A Powerfull Redis client library for D Programming Language.
Porting from java Jedis, support redis 3.x / 4.x all features and
5.x
some features.
So what can I do with Redis?
All of the following redis features are supported:
* Sorting
* Connection handling
* Commands operating on any
12 matches
Mail list logo
