On 2016-01-18 09:40, qznc wrote:
This "rc" is "reference counting"? Reference counting is also a form of
garbage collection ("gc"). So I don't like this classification. If we
really want "rc", then something like "trace" instead of "gc" should be
the alternative.
They are suggestions. More an
On Thursday, 14 January 2016 at 07:44:16 UTC, Jacob Carlborg
wrote:
std.experimental.memory.rc
std.experimental.memory.gc
std.experimental.memory.manual // or something
This "rc" is "reference counting"? Reference counting is also a
form of garbage collection ("gc"). So I don't like this
On Thursday, 14 January 2016 at 14:52:19 UTC, Andrei Alexandrescu
wrote:
On 01/14/2016 09:50 AM, bachmeier wrote:
On Thursday, 14 January 2016 at 07:44:16 UTC, Jacob Carlborg
wrote:
std.experimental.memory.rc
std.experimental.memory.gc
std.experimental.memory.manual // or something
+1
I
On Thursday, 14 January 2016 at 07:44:16 UTC, Jacob Carlborg
wrote:
On 2016-01-14 01:35, Andrei Alexandrescu wrote:
Hey folks, I want to push things forward with artifacts
dedicated to
avoiding the GC, and of course my main worry is finding the
right name.
An obvious choice is
On Saturday, 16 January 2016 at 15:56:39 UTC, karabuta wrote:
On Thursday, 14 January 2016 at 07:44:16 UTC, Jacob Carlborg
wrote:
std.experimental.memory.rc
std.experimental.memory.gc
std.experimental.memory.manual // or something
+1
Simplifies things IMO
On Thursday, 14 January 2016 at 00:35:53 UTC, Andrei Alexandrescu
wrote:
Hey folks, I want to push things forward with artifacts
dedicated to avoiding the GC, and of course my main worry is
finding the right name.
An obvious choice is std.experimental.nogc but we know from
Marketing 101 that
On 2016-01-14 15:52, Andrei Alexandrescu wrote:
I don't see how this categorization works. E.g. there's no need for
special tooling related to the GC. -- Andrei
It was just a couple of suggestions. I don't know exactly what you're
going to include in this module.
--
/Jacob Carlborg
On 01/14/2016 10:46 AM, Jacob Carlborg wrote:
On 2016-01-14 15:52, Andrei Alexandrescu wrote:
I don't see how this categorization works. E.g. there's no need for
special tooling related to the GC. -- Andrei
It was just a couple of suggestions. I don't know exactly what you're
going to
On Thursday, 14 January 2016 at 07:44:16 UTC, Jacob Carlborg
wrote:
std.experimental.memory with submodules for the different use
cases:
std.experimental.memory.rc
std.experimental.memory.gc
std.experimental.memory.manual // or something
Agreed.
On Thursday, 14 January 2016 at 00:35:53 UTC, Andrei Alexandrescu
wrote:
Ideas?
Andrei
std.experimental.rusty
On Thursday, 14 January 2016 at 07:44:16 UTC, Jacob Carlborg
wrote:
std.experimental.memory with submodules for the different use
cases:
std.experimental.memory.rc
std.experimental.memory.gc
std.experimental.memory.manual // or something
this has my vote
I guess the first submodule should
On Thursday, 14 January 2016 at 00:35:53 UTC, Andrei Alexandrescu
wrote:
Ideas?
import std.experimental.gcbypass;
import std.experimental.gcfreedom;
import std.experimental.shuntgc;
import std.experimental.rcinstead;
import std.experimental.manual;
On Thursday, 14 January 2016 at 02:13:20 UTC, Ilya wrote:
std.memory --Ilya
That's a good one.
On 01/14/2016 12:48 AM, Vladimir Panteleev wrote:
On Thursday, 14 January 2016 at 00:35:53 UTC, Andrei Alexandrescu wrote:
Hey folks, I want to push things forward with artifacts dedicated to
avoiding the GC, and of course my main worry is finding the right name.
An obvious choice is
On 15/01/16 5:11 AM, Andrei Alexandrescu wrote:
On 01/14/2016 10:46 AM, Jacob Carlborg wrote:
On 2016-01-14 15:52, Andrei Alexandrescu wrote:
I don't see how this categorization works. E.g. there's no need for
special tooling related to the GC. -- Andrei
It was just a couple of suggestions.
On 2016-01-14 17:11, Andrei Alexandrescu wrote:
Me neither, which adds to the problem :o). -- Andrei
You need to at least have some ideas, otherwise there's no point in a
new module :)
--
/Jacob Carlborg
On Thursday, 14 January 2016 at 07:44:16 UTC, Jacob Carlborg
wrote:
std.experimental.memory.rc
std.experimental.memory.gc
std.experimental.memory.manual // or something
+1
On 01/14/2016 09:50 AM, bachmeier wrote:
On Thursday, 14 January 2016 at 07:44:16 UTC, Jacob Carlborg wrote:
std.experimental.memory.rc
std.experimental.memory.gc
std.experimental.memory.manual // or something
+1
I don't see how this categorization works. E.g. there's no need for
special
On Thursday, 14 January 2016 at 00:35:53 UTC, Andrei Alexandrescu
wrote:
Hey folks, I want to push things forward with artifacts
dedicated to avoiding the GC, and of course my main worry is
finding the right name.
An obvious choice is std.experimental.nogc but we know from
Marketing 101 that
On 2016-01-14 01:35, Andrei Alexandrescu wrote:
Hey folks, I want to push things forward with artifacts dedicated to
avoiding the GC, and of course my main worry is finding the right name.
An obvious choice is std.experimental.nogc but we know from Marketing
101 that expressing something as a
On Thursday, 14 January 2016 at 00:35:53 UTC, Andrei Alexandrescu
wrote:
Hey folks, I want to push things forward with artifacts
dedicated to avoiding the GC, and of course my main worry is
finding the right name.
An obvious choice is std.experimental.nogc but we know from
Marketing 101 that
On Thursday, 14 January 2016 at 00:35:53 UTC, Andrei Alexandrescu
wrote:
Hey folks, I want to push things forward with artifacts
dedicated to avoiding the GC, and of course my main worry is
finding the right name.
std.samesamebutdifferent
On Thursday, 14 January 2016 at 00:35:53 UTC, Andrei Alexandrescu
wrote:
Hey folks, I want to push things forward with artifacts
dedicated to avoiding the GC, and of course my main worry is
finding the right name.
An obvious choice is std.experimental.nogc but we know from
Marketing 101 that
On Thursday, 14 January 2016 at 00:35:53 UTC, Andrei Alexandrescu
wrote:
Hey folks, I want to push things forward with artifacts
dedicated to avoiding the GC, and of course my main worry is
finding the right name.
An obvious choice is std.experimental.nogc but we know from
Marketing 101 that
On Thursday, 14 January 2016 at 00:35:53 UTC, Andrei Alexandrescu
wrote:
Hey folks, I want to push things forward with artifacts
dedicated to avoiding the GC, and of course my main worry is
finding the right name.
There are only two hard things in Computer Science: cache
invalidation and
Hey folks, I want to push things forward with artifacts dedicated to
avoiding the GC, and of course my main worry is finding the right name.
An obvious choice is std.experimental.nogc but we know from Marketing
101 that expressing something as a positive is better than a negative.
Another
On Thursday, 14 January 2016 at 00:35:53 UTC, Andrei Alexandrescu
wrote:
Hey folks, I want to push things forward with artifacts
dedicated to avoiding the GC, and of course my main worry is
finding the right name.
An obvious choice is std.experimental.nogc but we know from
Marketing 101 that
27 matches
Mail list logo
