Closed dylanahsmith closed 3 years ago
LGTM. But would be nice to test
2.6
,2.7
andruby-head
as well. It doesn't cost much.
The goal is to test this library, not ruby itself. Testing the earliest supported version ensures that we don't accidentally use features that were introduced later. Testing the latest ruby version helps catch the use of features that are deprecated or removed. Testing ruby-head or intermediate versions of ruby seems more like tests for ruby itself, unless we have version specific code.
Ideally, we would also test the earliest supported versions of other dependencies with the test for the earliest ruby version, but I wanted focus on fixing and migrating CI to start with.
Testing ruby-head or intermediate versions of ruby seems more like tests for ruby itself,
Sometimes you can hit subtle behavior difference that were introduced one version and reverted later. But whatever.
@casperisfine for review
This is mostly a backport of https://github.com/arthurnn/memcached/pull/185, https://github.com/arthurnn/memcached/pull/186 and https://github.com/arthurnn/memcached/pull/190
The only other change is the expectation of FrozenError gets raised when trying to mutate a frozen object.