Ibis Hotel Back Room
If you come into the Ibis, we are all kicked out of the lobby for being too loud. Just ho through the lobby to the back and you'll find us.
Re: Blog post on automem
On Friday, 28 April 2017 at 14:40:03 UTC, Mike Parker wrote:
Atila was kind enough to do a write up on his automem library
for the D Blog, talking about why he did it and showing some of
the implementation details. This is officially part of the GC
series. The next post in the series will be my @nogc post (I've
pushed it back to after DConf).
When I publish the next one, I'll add a page to the blog with
each post in the series linked under two categories: 'GC
Fundamentals' and 'Memory Management Strategies'. Atila's post
sits squarely in the latter. If you have a particular strategy
you use for working with D's GC, please let me know and we can
talk about a post (guest post or otherwise).
Blog:
https://dlang.org/blog/2017/04/28/automem-hands-free-raii-for-d/
Reddit:
https://www.reddit.com/r/programming/comments/682xzc/automem_a_library_for_cstyle_raii_in_d/
Does it possible to use the library with classes? I have a simple
code that can't be compiled due to GC calling.
import automem.unique : Unique;
import std.experimental.allocator.mallocator: Mallocator;
class MyClass {
int a;
this(int a) @nogc {
this.a = a;
}
~this() @nogc {
}
}
void main() @nogc
{
auto obj = Unique!(MyClass, Mallocator)(1);
}
Text of error is @nogc function 'D main' cannot call non-@nogc
destructor 'automem.unique.Unique!(MyClass,
Mallocator).Unique.~this'
Re: Blog post on automem
On 05/03/2017 01:05 PM, ANtlord wrote:
As far as I know a delegate depends on GC.
Closures depend on the GC. Not all delegates involve closures.
For example, you don't need the GC to make a delegate of a method:
struct S
{
int x = 0;
void m() @nogc { x = 1; }
}
void main() @nogc
{
S s;
void delegate() @nogc dg = &s.m;
dg();
assert(s.x == 1);
}
Re: Blog post on automem
On Friday, 28 April 2017 at 14:40:03 UTC, Mike Parker wrote: When I publish the next one, I'll add a page to the blog with each post in the series linked under two categories: 'GC Fundamentals' and 'Memory Management Strategies'. Atila's post sits squarely in the latter. If you have a particular strategy you use for working with D's GC, please let me know and we can talk about a post (guest post or otherwise). As far as I know a delegate depends on GC. Can this library help to solve this?
D IDE Coedit - released version 3 update 1
Hello, The latest major release does not contain any critical issue known at this day so this is a minor update that brings a few improvements mostly related to the edition: DDOC and completion (including an automatic mode, as suggested many times after latest release). - Changelog and dolwonad links: https://github.com/BBasile/Coedit/releases/tag/3_update_1 - Homepage: https://github.com/BBasile/Coedit - Manual:http://bbasile.github.io/Coedit/
