Re: how to mark an extern function @nogc?
On Wednesday, 13 July 2016 at 02:20:58 UTC, anonymous wrote: On Tuesday, 12 July 2016 at 14:04:55 UTC, Seb wrote: D is entirely driven by highly motivated volunteers. (this will change soon with the new D foundation) With the fundation, volunteers wont be highly motivated anymore. Fundations are real motivation-killers. I disagree. Volunteers will be motivated more, because D will now be more reliable as a thing they put their effort into and rely upon. Right now D is moving at relatively slow pace, because everybody works on it in their spare time. That also means they don't have spare time anymore. Somebody has to work on it full-time.
Re: how to mark an extern function @nogc?
On Wednesday, 13 July 2016 at 02:20:58 UTC, anonymous wrote: On Tuesday, 12 July 2016 at 14:04:55 UTC, Seb wrote: D is entirely driven by highly motivated volunteers. (this will change soon with the new D foundation) With the fundation, volunteers wont be highly motivated anymore. Fundations are real motivation-killers. I hope this won't be the case and there are successful cases (Linux, Python,...) which are still receiving many contributions by volunteers. However I am young and have not much experience, so I can just hope that Andrei and Walter find a good strategy. After all bringing money into development shouldn't have a negative impact.
Re: how to mark an extern function @nogc?
On Tuesday, 12 July 2016 at 14:04:55 UTC, Seb wrote: D is entirely driven by highly motivated volunteers. (this will change soon with the new D foundation) With the fundation, volunteers wont be highly motivated anymore. Fundations are real motivation-killers.
Re: how to mark an extern function @nogc?
On Tuesday, 12 July 2016 at 14:04:55 UTC, Seb wrote: D is entirely driven by highly motivated volunteers. (this will change soon with the new D foundation) I for one welcome our new D Foundation overlords.
Re: [OT] Re: how to mark an extern function @nogc?
On Tuesday, 12 July 2016 at 14:42:23 UTC, ag0aep6g wrote: On 07/12/2016 04:04 PM, Seb wrote: D is entirely driven by highly motivated volunteers. (this will change soon with the new D foundation) Does the foundation have plans to hire programmers? That's news to me. At the DConf16 Andrei announced in his keynote that he is in the progress of finding sponsors and has already made quite some progress (he mentioned 500K non-Zimbabwean dollars [1]), but also noticed that he still needs to built a roadmap & agenda on how to most effectively invest this money. I haven't heard much since, but I hope that once the D Foundation got an official non-profit status (according to the vision this is planned to happen in this August), we might hear more. Apart from that the D foundation currently already "hires" four programmers as part of the GSoC program ;-) [1] http://forum.dlang.org/post/qaskprdxmshpabara...@forum.dlang.org
[OT] Re: how to mark an extern function @nogc?
On 07/12/2016 04:04 PM, Seb wrote: D is entirely driven by highly motivated volunteers. (this will change soon with the new D foundation) Does the foundation have plans to hire programmers? That's news to me.
Re: how to mark an extern function @nogc?
On Tuesday, 12 July 2016 at 00:17:32 UTC, Adam Sansier wrote: On Monday, 11 July 2016 at 15:54:02 UTC, Seb wrote: On Monday, 11 July 2016 at 01:59:51 UTC, Adam Sansier wrote: On Monday, 11 July 2016 at 01:58:23 UTC, Adam Sansier wrote: I'm using some win functions that don't use the gc and are not marked, specifically CLSIDFromString that I imported myself(it's not marked nogc in objbase). I went ahead and copied the import and added nogc. Shouldn't someone add that to objbase? Why don't you fork it & add it yourself? Otherwise to quote Walter: "a bug only exists if it's on Bugzilla [issues.dlang.org]" ;-) If this is a bug then there are some serious issues with D's protocol of updating code. How can entire modules be missed? It seems the maintainers of D's library code do not actually use most of the features then? D needs a real code test suite to keep stuff like this from happening, not individual users from the outside to keep it in shape which makes me feel like a guinea pig. I won't stick around too long if that's the case. Well the code quality standards are actually quite high for D (and the test suites are there), but the problem that you discovered here is that most modules have been written before the moderately new @nogc keyword has been introduced. Phobos alone has > 100K LoC, so it just takes a bit of time until new features are propagated through the entire codebase and help is appreciated there because D is entirely driven by highly motivated volunteers. (this will change soon with the new D foundation) That being said (1) there are currently between 2-5 PRs per day to add more annotations to Phobos, (2) most code in Phobos is templated and thus the compiler can automatically infer attributes.
Re: how to mark an extern function @nogc?
On Monday, 11 July 2016 at 15:54:02 UTC, Seb wrote: On Monday, 11 July 2016 at 01:59:51 UTC, Adam Sansier wrote: On Monday, 11 July 2016 at 01:58:23 UTC, Adam Sansier wrote: I'm using some win functions that don't use the gc and are not marked, specifically CLSIDFromString that I imported myself(it's not marked nogc in objbase). I went ahead and copied the import and added nogc. Shouldn't someone add that to objbase? Why don't you fork it & add it yourself? Otherwise to quote Walter: "a bug only exists if it's on Bugzilla [issues.dlang.org]" ;-) If this is a bug then there are some serious issues with D's protocol of updating code. How can entire modules be missed? It seems the maintainers of D's library code do not actually use most of the features then? D needs a real code test suite to keep stuff like this from happening, not individual users from the outside to keep it in shape which makes me feel like a guinea pig. I won't stick around too long if that's the case.
Re: how to mark an extern function @nogc?
On Monday, 11 July 2016 at 15:54:02 UTC, Seb wrote: On Monday, 11 July 2016 at 01:59:51 UTC, Adam Sansier wrote: On Monday, 11 July 2016 at 01:58:23 UTC, Adam Sansier wrote: I'm using some win functions that don't use the gc and are not marked, specifically CLSIDFromString that I imported myself(it's not marked nogc in objbase). I went ahead and copied the import and added nogc. Shouldn't someone add that to objbase? Why don't you fork it & add it yourself? Otherwise to quote Walter: "a bug only exists if it's on Bugzilla [issues.dlang.org]" ;-) Unreported bugs can only be fixed by accident.
Re: how to mark an extern function @nogc?
On Monday, 11 July 2016 at 01:59:51 UTC, Adam Sansier wrote: On Monday, 11 July 2016 at 01:58:23 UTC, Adam Sansier wrote: I'm using some win functions that don't use the gc and are not marked, specifically CLSIDFromString that I imported myself(it's not marked nogc in objbase). I went ahead and copied the import and added nogc. Shouldn't someone add that to objbase? Why don't you fork it & add it yourself? Otherwise to quote Walter: "a bug only exists if it's on Bugzilla [issues.dlang.org]" ;-)
Re: how to mark an extern function @nogc?
On Monday, 11 July 2016 at 01:58:23 UTC, Adam Sansier wrote: I'm using some win functions that don't use the gc and are not marked, specifically CLSIDFromString that I imported myself(it's not marked nogc in objbase). I went ahead and copied the import and added nogc. Shouldn't someone add that to objbase?
how to mark an extern function @nogc?
I'm using some win functions that don't use the gc and are not marked, specifically CLSIDFromString that I imported myself(it's not marked nogc in objbase).
