http://d.puremagic.com/issues/show_bug.cgi?id=9071
monarchdo...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |monarchdo...@gmail.com
--- Comment #1 from monarchdo...@gmail.com 2012-11-25 03:15:54 PST ---
This is actually a problem with "hasSlicing": It is currently being tightened
so that the result of a slice operation *must* be convertible back to the
original type. If this is not the case, then the range will not be considered
sliceable.
Once this is deployed, you will (should) be forwarded to the "correct" overload
of sortImpl: The one that doesn't use slicing.
Still, could you please provide the code example that fails? This will help us
figure out which of the following is the culprit:
* The range?
* The definition of hasSlicing?
* The implementation of sort?
And correctly address the issue.
--
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
