hamcrest-as3 icon indicating copy to clipboard operation
hamcrest-as3 copied to clipboard

MXMLMatchers should cache internal matcher instances

Open drewbourne opened this issue 15 years ago • 0 comments

MXMLMatchers currently create a new instance of their internal matcher each time createMatcher() is called. In a performance sensitive scenario like rules engines this becomes prohibitively expensive in time, and memory. Cache the internal matcher until invalidated by property changes.

drewbourne avatar Apr 21 '10 12:04 drewbourne