In the first link I posted it shows something notable about using "delete" for deleting object properties:
In V8 6.0 and 6.1 (not yet used in any Node releases), deleting the last property added to an object hits a fast path in V8, and thus it is faster, even, than setting to undefined. This is excellent news, as it shows that the V8 team is working towards improving the performance of delete. However, the delete operator will still result in a significant performance hit on property access if a property *other than the most recently added property* is deleted from the object. So overall we have to continue to recommend against using delete. I've seen that it's used within the tiddlywiki core and the mentioned discovery appears to be a recent one @Jed Carty It's a bit annoying not knowing exactly where it goes and which tweaks made now are future-proof I hope that we can filter those tweaks that make sense so that we won't need to change again in half a year Simon -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/7751b600-26a5-4348-bbd9-7516fb85fdf9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
