On Tuesday, June 25, 2013 16:37:06 Jonathan M Davis wrote: > On Tuesday, June 25, 2013 21:42:17 Timon Gehr wrote: > > On 06/25/2013 09:21 PM, Jonathan M Davis wrote: > > > I suppose that takeExactly's Result type (in the case where it actually > > > creates its own type) could (and should) forward the primitives > > > associated > > > with hasMobileElements and hasAssignableElements (which it currently > > > doesn't), but that's all I can see that's missing. > > > ... > > > > (not properly propagating the underlying range's capabilities.) > > With regards to a couple of attributes that aren't even used much. Yes, they > should be propagated, but you seemed to be saying that there were big > problems with takeExactly, whereas the only issue is very minor, and it > would be very quick to fix it.
I would like to thank you for pointing out the missing propagation though. I suspect that those attributes are frequently forgotten. They're less critical than the main ones, but they should still be propagated appropriately. http://d.puremagic.com/issues/show_bug.cgi?id=10474 - Jonathan M Davis
