On 5/30/13 5:41 AM, Robin Berjon wrote: > This includes mutating them, and > behaving sanely in the face of mutation. A question is what constitutes sanity. > I'm very partial to C. The 5 should get pushed onto the array, and > whenever I look there in future it should still be right there, but any > control that is reflecting the status of that array should just ignore it. As opposed to just throwing an exception and being broken? That might be expensive to do. > All the libraries that do data binding (e.g. Angular, KnockOut) will do > something like that. What do they do if you push bogus values into the array? -BorisReceived on Thursday, 30 May 2013 14:20:16 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:13 UTC