On 17/08/11 5:05 AM, Jonathan M Davis wrote:
It was previously determined that this would be a problem for ranges which are
reference types (classes in particular, but it affects structs as well, if
copying them doesn't create an independent range). So, we added the save
property.
<snip>
Thoughts?
Apologies for my ignorance, but I haven't really been following all this
ranges stuff.
I must be missing something, why would you ever expect an algorithm that
works with value types to work with reference types as well?
