[Issue 5773] sort() and topN() fail on sliced/resized array of tuples
http://d.puremagic.com/issues/show_bug.cgi?id=5773 Andrei Alexandrescu changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Comment #6 from Andrei Alexandrescu 2013-01-07 23:38:59 PST --- Fixed as far back as 2.059. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 5773] sort() and topN() fail on sliced/resized array of tuples
http://d.puremagic.com/issues/show_bug.cgi?id=5773 --- Comment #4 from kenn...@gmail.com 2011-03-23 16:13:23 PDT --- The overlapping array copy exception should be the same as issue 5705. Not sure about the segfault, as I can't reproduce a segfault (only the same overlapping array copy exception is thrown). -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 5773] sort() and topN() fail on sliced/resized array of tuples
http://d.puremagic.com/issues/show_bug.cgi?id=5773
kenn...@gmail.com changed:
What|Removed |Added
CC||kenn...@gmail.com
--- Comment #3 from kenn...@gmail.com 2011-03-23 16:00:52 PDT ---
(In reply to comment #1)
> Perhaps this is just me being stupid -- trying to sort things that can't be
> compared? However, if I use a custom struct (instead of a tuple) I get an
> explicit compiler error about that (which is kind of useful ;-)
Except that Tuples *can* can compared. Example:
--
import std.typecons;
alias Tuple!(real,uint) Entry;
void main(){
assert(Entry(1.0, 4) > Entry(0.5, 9));
}
---
--
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
[Issue 5773] sort() and topN() fail on sliced/resized array of tuples
http://d.puremagic.com/issues/show_bug.cgi?id=5773 Andrei Alexandrescu changed: What|Removed |Added Status|NEW |ASSIGNED CC||and...@metalanguage.com AssignedTo|nob...@puremagic.com|and...@metalanguage.com --- Comment #2 from Andrei Alexandrescu 2011-03-23 15:19:12 PDT --- Thanks for the findings. They definitely point to bugs in sort and topN. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 5773] sort() and topN() fail on sliced/resized array of tuples
http://d.puremagic.com/issues/show_bug.cgi?id=5773 --- Comment #1 from Magnus Lie Hetland 2011-03-23 13:17:29 PDT --- Perhaps this is just me being stupid -- trying to sort things that can't be compared? However, if I use a custom struct (instead of a tuple) I get an explicit compiler error about that (which is kind of useful ;-) -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
