hamcrest-as3
hamcrest-as3 copied to clipboard
MXMLMatchers should cache internal matcher instances
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.