DConf 2017 livestream
As nobody posted this in the announce group yet, I'll just repeat this information here: The DConf 2017 livestream is available here: https://www.youtube.com/watch?v=MqrJZg6PgnM See the DLangConf twitter account for more information: https://twitter.com/DLangConf
Re: Blog post on automem
On Wednesday, 3 May 2017 at 12:43:26 UTC, ANtlord wrote:
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'
I took a look at this. It's a druntime problem. Unique.~this
calls std.experimental.allocator.dispose, which calls destroy in
object.d which calls rt_finalize:
extern (C) void rt_finalize(void *data, bool det=true);
Notice the lack of `@nogc` in the declaration. Adding the
annotation should fix the problem, assuming the implementation is
in fact `@nogc`. I'll file a bug and PR to fix it.
Atila
Re: DConf 2017 livestream
On Thursday, 4 May 2017 at 08:02:22 UTC, Johannes Pfau wrote: The DConf 2017 livestream is available here: https://www.youtube.com/watch?v=MqrJZg6PgnM Looks like the youtube video ID changes when the stream is stopped / restarted. Look for the livestream on https://www.youtube.com/user/sociomantic/feed or try https://www.youtube.com/user/sociomantic/live instead.
Re: Blog post on automem
On Thursday, 4 May 2017 at 08:41:55 UTC, Atila Neves wrote: I took a look at this. It's a druntime problem. Unique.~this calls std.experimental.allocator.dispose, which calls destroy in object.d which calls rt_finalize: extern (C) void rt_finalize(void *data, bool det=true); Notice the lack of `@nogc` in the declaration. Adding the annotation should fix the problem, assuming the implementation is in fact `@nogc`. I'll file a bug and PR to fix it. Bug: https://issues.dlang.org/show_bug.cgi?id=17297
Re: Blog post on automem
On Thursday, 4 May 2017 at 08:41:55 UTC, Atila Neves wrote: On Wednesday, 3 May 2017 at 12:43:26 UTC, ANtlord wrote: [...] I took a look at this. It's a druntime problem. Unique.~this calls std.experimental.allocator.dispose, which calls destroy in object.d which calls rt_finalize: extern (C) void rt_finalize(void *data, bool det=true); Notice the lack of `@nogc` in the declaration. Adding the annotation should fix the problem, assuming the implementation is in fact `@nogc`. I'll file a bug and PR to fix it. Atila There already is a bug, apparently: https://issues.dlang.org/show_bug.cgi?id=17297 Atila
DConf hackathon: idea list
Hi all, the DConf hackathon isn’t a hackathon in the traditional sense. It is intended as a day for _collaboratively_ focusing on long-lasting problems and pain points in the D ecosystem, planning upcoming features or DIPs, and creation of a rough roadmap for the next months. Of course, any D hackers who wish to simply progress their own personal projects are welcome too! Experience has shown that in large groups too much time is wasted on giving a voice to everyone, whereas for tiny groups chances are that it takes too long to get the ball rolling. Hence, a group size of four or five D hackers is recommended. Below you can find a list of themes with a short abstract and a couple of ideas. The abstracts and ideas are intended to get you started and guide you. Please feel free to _add your own ideas_ and _add your names_ next to them so that people can ping you (IRC, email, and other IM handles might be handy as well). Of course, you can add your name to multiple projects. On Sunday the first half an hour will be used to finalize the group forming. All existing groups and persons with an idea, but without a group can pitch their idea shortly (one minute max, no slides) and thus find other motivated D hackers. https://docs.google.com/document/d/1L5edu6LLj3Afa3tPgqk-aX-fErwr7sPj37Dt5avoc5w/edit#
Re: DConf hackathon: idea list
In short I want Phobos to have an image library and long with it a windowing lib (but lets ignore that last part for now). I welcome people stealing and creating a competing ideas for anything in [0] and [1] that I have. Alternatively you can also create PR's for anything there as well. There is also [2] which is the start of my fixed-sized linear algebra library for game development. Of note is my managed memory concept, it needs a full rewrite. I have yet to be able to use it to its full power with its managers (e.g. data structure knowing when memory is ready to die). There is a serializer in[1] that could do with a couple of iterations in becoming faster and more feature full. I will try my best to be available via IRC and on the N.G. but well New Zealand time zones and all that. If you have any questions or want some assistance, hit me up! Now let's destruct these ideas. [0] https://github.com/rikkimax/alphaPhobos/tree/master/source/std/experimental [1] https://github.com/Devisualization/spew/tree/master/src/base/cf/spew/serialization [2] https://gist.github.com/rikkimax/f5c0accd3463d52fda524f1f929b29ab
Re: DConf hackathon: idea list
On 5/4/17 15:32, Seb wrote: Hi all, the DConf hackathon isn’t a hackathon in the traditional sense. It is intended as a day for _collaboratively_ focusing on long-lasting problems and pain points in the D ecosystem, planning upcoming features or DIPs, and creation of a rough roadmap for the next months. Of course, any D hackers who wish to simply progress their own personal projects are welcome too! Experience has shown that in large groups too much time is wasted on giving a voice to everyone, whereas for tiny groups chances are that it takes too long to get the ball rolling. Hence, a group size of four or five D hackers is recommended. Below you can find a list of themes with a short abstract and a couple of ideas. The abstracts and ideas are intended to get you started and guide you. Please feel free to _add your own ideas_ and _add your names_ next to them so that people can ping you (IRC, email, and other IM handles might be handy as well). Of course, you can add your name to multiple projects. On Sunday the first half an hour will be used to finalize the group forming. All existing groups and persons with an idea, but without a group can pitch their idea shortly (one minute max, no slides) and thus find other motivated D hackers. https://docs.google.com/document/d/1L5edu6LLj3Afa3tPgqk-aX-fErwr7sPj37Dt5avoc5w/edit# From the Phobos wishlist: I am working an a generic SQL database interface. If anybody is interested in helping out I have a small amount of code that shows the general design direction I've taken so far. We can discuss the design and collaboratively hack out a prototype. The current code is here: https://github.com/LightBender/std.experimental.database.sql -- Adam Wilson IRC: LightBender import quiet.dlang.dev;
Re: DConf hackathon: idea list
On 04/05/2017 3:22 PM, Adam Wilson wrote: On 5/4/17 15:32, Seb wrote: Hi all, the DConf hackathon isn’t a hackathon in the traditional sense. It is intended as a day for _collaboratively_ focusing on long-lasting problems and pain points in the D ecosystem, planning upcoming features or DIPs, and creation of a rough roadmap for the next months. Of course, any D hackers who wish to simply progress their own personal projects are welcome too! Experience has shown that in large groups too much time is wasted on giving a voice to everyone, whereas for tiny groups chances are that it takes too long to get the ball rolling. Hence, a group size of four or five D hackers is recommended. Below you can find a list of themes with a short abstract and a couple of ideas. The abstracts and ideas are intended to get you started and guide you. Please feel free to _add your own ideas_ and _add your names_ next to them so that people can ping you (IRC, email, and other IM handles might be handy as well). Of course, you can add your name to multiple projects. On Sunday the first half an hour will be used to finalize the group forming. All existing groups and persons with an idea, but without a group can pitch their idea shortly (one minute max, no slides) and thus find other motivated D hackers. https://docs.google.com/document/d/1L5edu6LLj3Afa3tPgqk-aX-fErwr7sPj37Dt5avoc5w/edit# From the Phobos wishlist: I am working an a generic SQL database interface. If anybody is interested in helping out I have a small amount of code that shows the general design direction I've taken so far. We can discuss the design and collaboratively hack out a prototype. The current code is here: https://github.com/LightBender/std.experimental.database.sql Looking at that I think focusing on describing of tables ext. would be a good first step. I worry that it won't be very flexible memory management or serialization wise.
Re: DConf hackathon: idea list
I just added two things: 1) error messages, which are code intensive but a HUGE payoff in productivity (and thus marketing) and 2) Opposite attributes, which are trivial to implement but painful to get merged. I think dconf is a good opportunity for you guys to get things like #2 actually merged. No more waiting for months for a review, discuss it right there and have an in-person decision to go or not go. Merge immediately without additional delay.
Re: DConf hackathon: idea list
On Thursday, 4 May 2017 at 14:53:34 UTC, Adam D. Ruppe wrote: I just added two things: 1) error messages, which are code intensive but a HUGE payoff in productivity (and thus marketing) and 2) Opposite attributes, which are trivial to implement but painful to get merged. I think dconf is a good opportunity for you guys to get things like #2 actually merged. No more waiting for months for a review, discuss it right there and have an in-person decision to go or not go. Merge immediately without additional delay. I just had a vision: pragma(pushAttributes); @safe: void foo(); pragma(popAttributes); void notsafeanymore(); No need for reverse for each attribute (and new attributes in the future).
Re: DConf hackathon: idea list
On 04/05/2017 4:29 PM, OoopsAgain wrote:
On Thursday, 4 May 2017 at 14:53:34 UTC, Adam D. Ruppe wrote:
I just added two things:
1) error messages, which are code intensive but a HUGE payoff in
productivity (and thus marketing)
and 2) Opposite attributes, which are trivial to implement but painful
to get merged.
I think dconf is a good opportunity for you guys to get things like #2
actually merged. No more waiting for months for a review, discuss it
right there and have an in-person decision to go or not go. Merge
immediately without additional delay.
I just had a vision:
pragma(pushAttributes);
@safe: void foo();
pragma(popAttributes);
void notsafeanymore();
No need for reverse for each attribute (and new attributes in the future).
So:
@safe {
void foo();
}
void notsafeanymore();
Re: DConf hackathon: idea list
On Thursday, 4 May 2017 at 15:40:57 UTC, rikki cattermole wrote:
On 04/05/2017 4:29 PM, OoopsAgain wrote:
On Thursday, 4 May 2017 at 14:53:34 UTC, Adam D. Ruppe wrote:
[...]
I just had a vision:
pragma(pushAttributes);
@safe: void foo();
pragma(popAttributes);
void notsafeanymore();
No need for reverse for each attribute (and new attributes in
the future).
So:
@safe {
void foo();
}
void notsafeanymore();
I suppose this would be fundamentally implemented in this way:
new scope with scope attridfgjlkdg,;
Re: DConf 2017 livestream
On Thursday, 4 May 2017 at 09:29:01 UTC, Johannes Pfau wrote: Looks like the youtube video ID changes when the stream is for the late comers, meanwhile the videos are getting ready and posted on youtube, it would be nice to post all those ids here. because it seems only those with a link can access todays recordings, on the channel' page there's only dating videos.
Re: DConf 2017 livestream
On Friday, 5 May 2017 at 01:43:15 UTC, سليمان السهمي (Soulaïman Sahmi) wrote: On Thursday, 4 May 2017 at 09:29:01 UTC, Johannes Pfau wrote: Looks like the youtube video ID changes when the stream is for the late comers, meanwhile the videos are getting ready and posted on youtube, it would be nice to post all those ids here. because it seems only those with a link can access todays recordings, on the channel' page there's only dating videos. If you use either of the Sociomantic live links he gave while the stream is live, that will show it to you. As for the archived stream, yes, you need the youtube video ids to view the pieces of that stream, as those videos are not public. They will be chopped up and made into public videos soon. If you can't wait, those archived stream ids have been posted in the General forum.
Re: DConf 2017 livestream
On Friday, 5 May 2017 at 04:00:14 UTC, Joakim wrote: On Friday, 5 May 2017 at 01:43:15 UTC, سليمان السهمي (Soulaïman Sahmi) wrote: ... If you can't wait, those archived stream ids have been posted in the General forum. What I was looking for. Thank you.
