D issues are now tracked on GitHub. This Bugzilla instance remains as a read-only archive.
Issue 7029 - std.container.Array cannot use insertAfter
Summary: std.container.Array cannot use insertAfter
Status: RESOLVED WORKSFORME
Alias: None
Product: D
Classification: Unclassified
Component: phobos (show other issues)
Version: D2
Hardware: Other Windows
: P2 normal
Assignee: No Owner
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-29 07:20 UTC by SHOO
Modified: 2014-02-18 05:22 UTC (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description SHOO 2011-11-29 07:20:16 UTC 
This code cannot compile!

import std.container;
void main()
{
	Array!int ary;
	ary.insertAfter(ary[], 1); // <- NG
}
Comment 2 SHOO 2011-12-01 06:45:49 UTC 
Oops! My bad.
Comment 3 Peter Alexander 2014-02-16 14:03:22 UTC 
Can't find the specific pull, but this was fixed in 2.060

http://dpaste.dzfl.pl/09dba06c8ff3
Comment 4 Andrej Mitrovic 2014-02-16 14:06:11 UTC 
Resolve it as WORKSFORME when the pull is missing.
Comment 5 Peter Alexander 2014-02-16 14:10:21 UTC 
(In reply to comment #4)
> Resolve it as WORKSFORME when the pull is missing.

I thought WORKSFORME is for when the original bug actually works and the user has just made a mistake or the bug otherwise cannot be reproduced?

(do we have guidelines for this?)
Comment 6 Andrej Mitrovic 2014-02-16 14:14:29 UTC 
(In reply to comment #5)
> (In reply to comment #4)
> > Resolve it as WORKSFORME when the pull is missing.
> 
> I thought WORKSFORME is for when the original bug actually works and the user
> has just made a mistake or the bug otherwise cannot be reproduced?

There's INVALID for that.

> (do we have guidelines for this?)

The (current) problem is that bugs marked as FIXED will end up in the changelog for the upcoming release. There may be a way around this if we change the changelog generator tool to filter through git commits rather than query bugzilla, but it hasn't been done yet.
Comment 7 Peter Alexander 2014-02-16 14:18:10 UTC 
(In reply to comment #6)
> The (current) problem is that bugs marked as FIXED will end up in the changelog
> for the upcoming release. There may be a way around this if we change the
> changelog generator tool to filter through git commits rather than query
> bugzilla, but it hasn't been done yet.

Fair enough. Looks like I'll need to go back over some of my resolves :-)
Comment 8 yebblies 2014-02-18 05:22:39 UTC 
(In reply to comment #5)
> (In reply to comment #4)
> > Resolve it as WORKSFORME when the pull is missing.
> 
> I thought WORKSFORME is for when the original bug actually works and the user
> has just made a mistake or the bug otherwise cannot be reproduced?
> 
> (do we have guidelines for this?)

Yes, we do!

The "Status" label above links to this:
https://d.puremagic.com/issues/page.cgi?id=fields.html#status

So basically WORKSFORME means both 'cannot reproduce' and 'can no longer reproduce' and so is valid for a bug where the fix is unknown.