"Brad Anderson"  wrote in message news:wngrzrehfxalejkrurbw@forum.dlang.org...

> 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

Not exactly.  Once I get it all set up, converting a pull request to D will be fairly automatic.

The recent refactoring broke many pulls over and over again, while the D switch will break all of them only once. 

On Wednesday, 26 February 2014 at 10:36:14 UTC, Per Nordlöw wrote:
> Make it possible to defined implicit conversions between wrapped types in order to, for instance, correctly implement NotNull for reference types.

I'm pretty sure multiple alias this would do the trick.

interface A {}
interface B {}
class C : A, B {}
class D : C {}

NotNull!D should implicitly cast to NotNull!C AND to D (the latter gives access to the methods here too so it should be preferred).

NotNull!C should implicitly cast to C (the first one to try), NotNull!A, NotNull!B, and NotNull!Object.

Multiple alias this would allow that.

https://d.puremagic.com/issues/show_bug.cgi?id=6083

On Wednesday, 26 February 2014 at 01:34:36 UTC, Mike wrote:
> On Wednesday, 26 February 2014 at 01:32:43 UTC, Mike wrote:
>> I created an enhancement request here: https://d.puremagic.com/issues/post_bug.cgi.
>
> Damn! Here's the correct link: https://d.puremagic.com/issues/show_bug.cgi?id=12259
>
> Mike

You didn't explain why you need this feature and its benefits. Allowing multiple
votes per user obviously skews the results and defeats the
purpose of voting.

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. :)

I'm not in a hurry seeing this added to D. In fact, I think we
should wait a few years for C++ feedback on this feature. It
might be that in a couple of years, the gen eral consensus is
that it was not such a great idea after all, or that the
implementation could have been improved in such or such way. The
current body of experience is not large enough for a clear view.

On Saturday, 1 March 2014 at 03:47:37 UTC, SomeDude wrote:
> You didn't explain why you need this feature and its benefits.

I didn't think an explanation was necessary, but ok.

Right now there's no way to quantify your preference.  You can
only say you want the bug fixed or you don't.  You don't get to
say how badly you want it fixed.  Being able allocate more of
your allowance to something allows you to quantify its value.  To
allocate more towards one issue gives you less to allocate
towards other issues.

"The cost of something is what you give up to get it" -
Principles of Economics, Translated by Yoram Bauman
http://www.youtube.com/watch?v=VVp8UGjECt4

You'll probably find this educational and enter

> Allowing multiple
> votes per user obviously skews the results and defeats the
> purpose of voting.

Yeah, "obviously" it is I who doesn't understand.

On Saturday, 1 March 2014 at 05:00:08 UTC, Mike wrote:
> On Saturday, 1 March 2014 at 03:47:37 UTC, SomeDude wrote:
>> You didn't explain why you need this feature and its benefits.
>
> I didn't think an explanation was necessary, but ok.
>
> Right now there's no way to quantify your preference.  You can
> only say you want the bug fixed or you don't.  You don't get to
> say how badly you want it fixed.  Being able allocate more of
> your allowance to something allows you to quantify its value.  To
> allocate more towards one issue gives you less to allocate
> towards other issues.

I didn't get it was in the context of keeping a limited number of
possible votes. I understood the original request was to remove
the cap on votes/person. Those two features are mutually
exclusive.

What coud be also possible is capping a number of
votes/person/month (if the system allws that). That would allow
someone to cast 12 votes/year on a single bug.

Still, I don't like the idea of someone casting several votes on
a bug, unless we also display the number of different voters next
to the total number of votes. Because a bug with 10 votes from 10
different voters is arguably more important than a bug with 10
votes by a single voter.

Fix issue 12256 / 9335 (http://forum.dlang.org/thread/bug-12256-3@https.d.puremagic.com%2Fissues%2F & https://d.puremagic.com/issues/show_bug.cgi?id=9335)

Since I use shared pointer, it is a torture to work with D built-in arrays / AA's. :/

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

1. const inference for template parameters.
https://d.puremagic.com/issues/show_bug.cgi?id=7521

2. Fix CTFE memory usage.
https://d.puremagic.com/issues/show_bug.cgi?id=6498

3. const correctness of object (new design)
https://d.puremagic.com/issues/show_bug.cgi?id=1824

On 02/25/2014 06:00 AM, 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.

Just another wishlist thread?
Clearly for a roadmap you have to match demand with possible supply.
If you want to implement something or you found someone to do it for you put it on the Agenda (http://wiki.dlang.org/Agenda).

> 1. Options to select CRT reference for DMD-Win64, and /Zl equiv option
> to omit any such reference.
Not sure what this is for, won't -defaultlib= + manual linking already do the job? Is this very important or just a personal issue of yours?

> 2. **Debugging**; concerted focus to tighten the experience. Classes,
> enums, globals (and more) all don't work. Locals with the same name
> appearing in multiple sub-scope's within the same function confuse the
> debugger. Control statements (break, continue, etc) don't seem to emit
> line numbers; single stepping skips right over them.
Debugging is important, but personally I have no interest to work on Windows debug information. Your best bet is to pair up with Rainer who already has a lot to do maintaining VisualD.

> 3. ref doesn't accept rvalues. Can't declare ref locals (pointers change
> semantics).
There seem to be competing DIPs. Please assemble the available information and any existing discussion outcome and update the wiki accordingly.
Also this might need a final discussion/voting round and at least a glance from Walter and Andrei.
If Kenji has enough time, he might be able to help you with the implementation.

On Saturday, 1 March 2014 at 23:51:32 UTC, Martin Nowak wrote:
> Just another wishlist thread?
> Clearly for a roadmap you have to match demand with possible supply.
> If you want to implement something or you found someone to do it for you put it on the Agenda (http://wiki.dlang.org/Agenda).

Does everything on this list actually have someone willing to implement it? There's a lot of good stuff here.