Several steps were made to achieve mutant working with Ruby 2.4 without
warnings and spec failures:
* Fix Fixnum deprecation warning
* Update RuboCop to 0.47 and fix offenses
* Relax version requirements on parser gem
* Update diff-lcs to 1.3
* Update rake 11.x -> 12.x
* Update reek 4.5 -> 4.6 (to work with parser 2.4)
* Update json 2.0 -> 2.1
* Update parallel 1.10 -> 1.11
* Update simplecov 0.12 -> 0.14
* Run regexp_parser integration against v0.4.3 (as we requiring this
exact version)
* Update warnings.yml with new whitelist
* Run CircleCI tests on Ruby 2.3 and 2.4 (Bundler.with_clean_env
was causing troubles on new CircleCI 2.0 setup, so it was removed)
* Avoids boot time mutation of REGISTER constant
* Allows to define project specific expression parsing
* Avoids custom (slow) serialization of Expression objects speeding up
reporter / killer IPC
* Improve specification
* Improve integration API as it now finally references an object the config
* Allow reproduction of syntax from Expression#syntax
* Allow instantiation of Expresssion objects without generating the
syntax, much nicer for most specs & internal code, avoids generating
a string to parse it into an expression
* Fix LSP violation in Mutant::Matcher namespace
* Before Mutant::Expression was not marshallable resulting in the need
to build "partial" result objects from killforks.
* Fixes an adjacent bug in spec selection
* Add Mutant::AST namespace to hold all AST related data / helpers.
* Mutant::AST will be externalized into an ast-meta gem that can be
shared with unparser for deduplication.
* Over the time the mutators itself will not need to deal with semantic
analysis of the AST anymore by themselves.
* Move AST analysis for send nodes to AST::Meta
* Fix#209
