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 possibility is std.experimental.rc, but that's imprecise because the artifacts in there will contain a variety of things in addition to reference counting-related artifacts.

Ideas?


Andrei

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 expressing something as a positive is better than a negative. Another possibility is std.experimental.rc, but that's imprecise because the artifacts in there will contain a variety of things in addition to reference counting-related artifacts.
>
> Ideas?
>
>
> Andrei

std.experimental.mm ?
mm => memory management

It would be interesting to know what you plan on putting in there. There's a few functions that duplicate utility in Phobos but one allocates and the other doesn't — e.g, lineSplitter. lineSplitter is 4-5x faster than the equivalent GC version(splitLines) according to my benchmarks.

I think one of the bigger issues with Phobos using the GC isn't that it uses the GC, but many functions allocate far more than they need to. I've seen Rust referred to as too focused on memory management(in fact, I think it was you that referred to Rust as this) but I think D sometimes goes in the opposite direction making it too easy to forget about memory management and just allocate everywhere because it's very implicit.

Bye.

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 expressing something as a positive is better than a negative. Another possibility is std.experimental.rc, but that's imprecise because the artifacts in there will contain a variety of things in addition to reference counting-related artifacts.
>
> Ideas?
>
>
> Andrei

std.experimental.gcfree
std.experimental.unmanaged
std.experimental.uncollected
std.experimental.mmm (manual mem managment)

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 expressing something as a positive is better than a negative. Another possibility is std.experimental.rc, but that's imprecise because the artifacts in there will contain a variety of things in addition to reference counting-related artifacts.
>
> Ideas?
>
>
> Andrei

std.memory --Ilya

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 expressing something as a positive is better than a negative. Another possibility is std.experimental.rc, but that's imprecise because the artifacts in there will contain a variety of things in addition to reference counting-related artifacts.
>
> Ideas?
>
>
> Andrei

Aside from that, naming it std.experimental.nogc is a bad idea because it'll
confuse newcomers, thinking it's somehow related to @nogc... Which it is, but
we don't want people importing std.experimental.nogc because they think they
need to do that to use @nogc.

Ideas:

std.experimental.gcless (still negative)
std.experimental.gcfree
std.experimental.realtime
std.experimental.pausefree
std.experimental.manualheap
std.experimental.manualmem

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 naming things. -- Phil Karlton

I'd go with std.memory or std.memory_management as others have suggested.

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 expressing something as a positive is better than a negative. Another possibility is std.experimental.rc, but that's imprecise because the artifacts in there will contain a variety of things in addition to reference counting-related artifacts.
>
> Ideas?

std.experimental.lifetime

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 positive is better than a negative.
> Another possibility is std.experimental.rc, but that's imprecise because
> the artifacts in there will contain a variety of things in addition to
> reference counting-related artifacts.

std.experimental.memory with submodules for the different use cases:

std.experimental.memory.rc
std.experimental.memory.gc
std.experimental.memory.manual // or something

-- 
/Jacob Carlborg

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.