This will allow to use reporters from matchers avoiding stupid direct
writes to $stderr.
Also it will allow to remove matching from CLI altogether in a phase of
the runner. Allowing to decouple Mutant::Config from VM environment
allowing to serialize it ;)
Step by step. Takes a while.
* I do not use 1.9.3
* Also keeping them in each file increases mental overhead (true it *can* be autoamted)
* None of the files encodes NON ASCII chars.
* I do not expect it makes any difference, since nobody programmatically
will consume strings generated by mutant under the assumption they are UTF-8 encoded.
* 1.9.3 Users have to deal with the encoding fuckup under ruby anyways.
"Many" library authors override Class or Modules #name not to return a
String or nil. They are not aware these are integral APIs for
reflection / tools. This change prints an ugly warning message in case
the API was violated.
Mutant used to crash often because of this LSP violation. This change
should provide a generic workaround.
* Classifiers are matcher subclass and delegate to lazy builded matcher
interfaces
* Solves chicken egg problem between target library load and classifier
matcher instantiation
2013-01-21 20:08:30 +01:00
Renamed from lib/mutant/matcher/object_space.rb (Browse further)
