Top-3 for 2.066 (page 2)

> 3. ref doesn't accept rvalues. Can't declare ref locals (pointers change > semantics). > > These above anything else are interfering with my work every day. > > What are yours? Every year again: rvalue references. :)

On Tuesday, 25 February 2014 at 05:01:30 UTC, Manu wrote: > In lieu of a clear roadmap, I'm just going to list the things actively > holding me up on a daily basis. > Others encouraged to add theirs, maybe we'll see patterns emerge. > > > What are yours? Enhanced privacy: https://d.puremagic.com/issues/show_bug.cgi?id=1238 https://d.puremagic.com/issues/show_bug.cgi?id=5770 https://d.puremagic.com/issues/show_bug.cgi?id=11234 etc.

On Tuesday, 25 February 2014 at 12:35:18 UTC, Namespace wrote: >> 3. ref doesn't accept rvalues. Can't declare ref locals (pointers change >> semantics). >> >> These above anything else are interfering with my work every day. >> >> What are yours? > > Every year again: rvalue references. :) +1 for this too ! Add struct default constructors that execute code!!!

shared libraries on OSX: https://d.puremagic.com/issues/show_bug.cgi?id=12190 runtime loaded shared library on osx: partially worked in 2.062, fails since 2.063 Also, this was marked as fixed (with bounty :) ): https://d.puremagic.com/issues/show_bug.cgi?id=11478 shared library on osx: worked in 2.062, fails in 2.063.2, still fails in 2.064 but there still seems to be issues: see last comment ("It's supposed to print that, because shared libraries aren't yet supported on OSX.") On Tue, Feb 25, 2014 at 6:54 AM, Remo <remo4d@gmail.com> wrote: > On Tuesday, 25 February 2014 at 12:35:18 UTC, Namespace wrote: > >> 3. ref doesn't accept rvalues. Can't declare ref locals (pointers change >>> semantics). >>> >>> These above anything else are interfering with my work every day. >>> >>> What are yours? >>> >> >> Every year again: rvalue references. :) >> > > +1 for this too ! > > Add struct default constructors that execute > code!!! >

On 26 February 2014 01:54, Timothee Cour <thelastmammoth@gmail.com> wrote: > shared libraries on OSX: > Oh yeah, that one's critical on all platforms. But as far as I can tell, that one is being actively worked on, and moving as fast as it moves. https://d.puremagic.com/issues/show_bug.cgi?id=12190 > runtime loaded shared library on osx: partially worked in 2.062, fails since 2.063 > > > Also, this was marked as fixed (with bounty :) ): > https://d.puremagic.com/issues/show_bug.cgi?id=11478 > shared library on osx: worked in 2.062, fails in 2.063.2, still fails in > 2.064 > > but there still seems to be issues: see last comment ("It's supposed to print that, because shared libraries aren't yet supported on OSX.") > > > > On Tue, Feb 25, 2014 at 6:54 AM, Remo <remo4d@gmail.com> wrote: > >> On Tuesday, 25 February 2014 at 12:35:18 UTC, Namespace wrote: >> >>> 3. ref doesn't accept rvalues. Can't declare ref locals (pointers change >>>> semantics). >>>> >>>> These above anything else are interfering with my work every day. >>>> >>>> What are yours? >>>> >>> >>> Every year again: rvalue references. :) >>> >> >> +1 for this too ! >> >> Add struct default constructors that execute >> code!!! >> > >

On Tuesday, 25 February 2014 at 09:08:05 UTC, Mike wrote: > 3. All pull requests older than 6 months acted upon, or closed With the Daniel Murphy's completion[1] of his refactoring of the DMDFE in order to begin converting the D frontend to D this item has become more important for that transition to go smoothly, I suspect. 1. https://github.com/D-Programming-Language/dmd/pull/1980#issuecomment-35830996

February 25, 2014

Re: Top-3 for 2.066

Posted by Joseph Cassman
in reply to Manu

Permalink

Joseph Cassman

Posted in reply to Manu

Permalink

On Tuesday, 25 February 2014 at 05:01:30 UTC, Manu wrote:
> What are yours?

The stuff listed on the wiki agenda (http://wiki.dlang.org/Agenda) is nice and will definitely make the language cleaner. However for me there are two elephants in the room.

A major argument in favor of Go tends to be focused around its straightforward parallelism support. D's support is good but not yet as straightforward. I like ranges. But I would also like to be able to use yield (a la coroutines) + async/await (from .NET). Making this work seamlessly with std.parallelism and integrating it directly into the language (similar to how threads currently are) would really make D a slam dunk. Along with this, std.parallelism's performance could be improved to the point where there is no more concern about it being as fast as green-thread implementations in other languages.

Here are two recent threads that discuss this topic.

http://forum.dlang.org/thread/mailman.126.1390929933.13884.digitalmars-d@puremagic.com
http://forum.dlang.org/thread/teiustvtqwcvdmmmdbqo@forum.dlang.org

The second elephant is memory usage. Based on recent discussions on the possible use of ARC/scopebuffer/std.allocator/etc. it seems that soon Phobos will get some major assistance in this regard. Awesome. Really looking forward too to the GC improvements and integration of the up-and-coming allocator module.

Here are two threads talking about memory usage.

scopebuffer - http://forum.dlang.org/thread/ld2586$17f6$1@digitalmars.com
tracing api - http://forum.dlang.org/thread/l8lup8$2bgl$1@digitalmars.com

The following links are encouraging. They show Andrei's statements on the need to focus on memory allocation right now.

http://forum.dlang.org/thread/grngmshdtwqfaftefhky@forum.dlang.org?page=11#post-lclta7:241rdg:241:40digitalmars.com
http://forum.dlang.org/thread/grngmshdtwqfaftefhky@forum.dlang.org?page=14#post-lcoskl:241g8t:241:40digitalmars.com

> I think of the following foci for the first half of 2014:
> 
> 1. Add @nullable and provide a -nullable compiler flag to verify it. The attribute is inferred locally and for white-box functions (lambdas, templates), and required as annotation otherwise. References not annotated with @nullable are statically enforced to never be null.
> 
> 2. Work on Phobos to see what can be done about avoiding unnecessary allocation. Most likely we'll need to also add a @nogc flag.
> 
> 3. Work on adding tracing capabilities to allocators and see how to integrate them with the language and Phobos.
> 
> 4. Work on the core language and druntime to see how to seamlessly accommodate alternate GC mechanisms such as reference counting.
> 
> 
> Andrei

These are the two big things that I am hoping will get some attention.

Thanks

Joseph

On Tuesday, 25 February 2014 at 12:35:18 UTC, Namespace wrote: >> 3. ref doesn't accept rvalues. Can't declare ref locals (pointers change >> semantics). >> >> These above anything else are interfering with my work every day. >> >> What are yours? > > Every year again: rvalue references. :) +1 Did a solution come out of this thread? http://forum.dlang.org/thread/km3k8v$80p$1@digitalmars.com?page=1 is it dip39? http://wiki.dlang.org/DIP39

On Tuesday, 25 February 2014 at 18:14:07 UTC, michaelc37 wrote: > On Tuesday, 25 February 2014 at 12:35:18 UTC, Namespace wrote: >>> 3. ref doesn't accept rvalues. Can't declare ref locals (pointers change >>> semantics). >>> >>> These above anything else are interfering with my work every day. >>> >>> What are yours? >> >> Every year again: rvalue references. :) > +1 > > Did a solution come out of this thread? > http://forum.dlang.org/thread/km3k8v$80p$1@digitalmars.com?page=1 > > is it dip39? > http://wiki.dlang.org/DIP39 No Andrei insist on his proposed solution which works already for templates: auto ref But nobody has implemented a good enough proposal which convinced him and Walter. I tried something nearly a year ago: http://forum.dlang.org/thread/ntsyfhesnywfxvzbemwc@forum.dlang.org#post-ntsyfhesnywfxvzbemwc:40forum.dlang.org It resulted in DIP 36: http://wiki.dlang.org/DIP36 which was rejected.

Forums