Hi Tobias. > Never seen or generated any performance test results myself however: > Jeremy claims it will be significantly more performant without the > extra conditional.
IMO avoiding redundancy is worth more than the minimal speed increment that results from a single comparison step. On this level one could also argue that it is not optimal to use ".forEach()" instead of a plain js for-loop since it will execute a function on every iteration step (in this case the performance drawback can be reduced by the optimizing compiler though, but this depends on the browser and whether the api-user provided callback function can be optimized). Also what could be done to increment the speed of filters is to cache all object properties like e.g. "operator.operand.length" and access them as variables in the iterator function. -Felix -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikidev+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywikidev@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/BLU436-SMTP127B8EEA7905F12B83198CECE300%40phx.gbl. For more options, visit https://groups.google.com/d/optout.
