← Back to index | Original Bugzilla link

Bug 7029 – std.container.Array cannot use insertAfter

Status
RESOLVED
Resolution
WORKSFORME
Severity
normal
Priority
P2
Component
phobos
Product
D
Version
D2
Platform
Other
OS
Windows
Creation time
2011-11-29T07:20:00Z
Last change time
2014-02-18T05:22:39Z
Assigned to
nobody
Creator
zan77137

Comments

Comment #0 by zan77137 — 2011-11-29T07:20:16Z
This code cannot compile! import std.container; void main() { Array!int ary; ary.insertAfter(ary[], 1); // <- NG }
Comment #1 by zan77137 — 2011-12-01T06:44:37Z
https://github.com/D-Programming-Language/druntime/pull/92
Comment #2 by zan77137 — 2011-12-01T06:45:49Z
Oops! My bad.
Comment #3 by peter.alexander.au — 2014-02-16T14:03:22Z
Can't find the specific pull, but this was fixed in 2.060 http://dpaste.dzfl.pl/09dba06c8ff3
Comment #4 by andrej.mitrovich — 2014-02-16T14:06:11Z
Resolve it as WORKSFORME when the pull is missing.
Comment #5 by peter.alexander.au — 2014-02-16T14:10:21Z
(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 by andrej.mitrovich — 2014-02-16T14:14:29Z
(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 by peter.alexander.au — 2014-02-16T14:18:10Z
(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 by yebblies — 2014-02-18T05:22:39Z
(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.