On Tuesday, 1 April 2014 at 15:16:41 UTC, Meta wrote:
On Tuesday, 1 April 2014 at 13:55:05 UTC, monarch_dodra wrote:
On Tuesday, 1 April 2014 at 13:54:00 UTC, monarch_dodra wrote:
In contrast, if you *pass* "1" to the DList, you lose that
info, and the DList will complain that you are trying to
assign an int to a ubyte.
EDIT: The issue is actually one of template constraint, but
it's
essentially equivalent. Without context you can't assign an int
to a ubyte.
I thought that maybe VRP might work here (as you detailed in
your other post), as it works elsewhere. Is is possible to
extend VRP to cover this situation?
*Maybe*, but it would require getting rid of the constraints.
However, those template constraints are necessary to resolve the
overloads to begin with ("insertBack(value)" vs
"insertBack(range)"). So VRP wouldn't even get a chance to
trigger :/
