diff options
| author | utilum <oz@utilum.com> | 2018-05-20 21:22:03 +0200 |
|---|---|---|
| committer | utilum <oz@utilum.com> | 2018-05-22 14:38:19 +0200 |
| commit | 0fcb921a65e615c301450d7820b03473acd53898 (patch) | |
| tree | 8cf5eea647e937b2576d7c5fb058c4e13b6d2dd9 /actionpack/lib/action_dispatch/middleware/session | |
| parent | 6c574ac58993512f975ddaf1f679c5956cc576df (diff) | |
| download | rails-0fcb921a65e615c301450d7820b03473acd53898.tar.gz rails-0fcb921a65e615c301450d7820b03473acd53898.tar.bz2 rails-0fcb921a65e615c301450d7820b03473acd53898.zip | |
Allow Range#=== and Range#cover? on Range
ruby/ruby@989e07c features switching `Range#===` to use internal `r_cover_p`
instead of rubyland `include?`. This breaks expected behavior of
`ActiveSupport::CoreExt::Range` documented since at least 8b67a02.
This patch adds overrides on `Range#cover?` and `Range#===` and places all
three in a single module, `CompareWithRange`.
*Requiring core_ext/range/include_range now causes a deprecation warnning*
Diffstat (limited to 'actionpack/lib/action_dispatch/middleware/session')
0 files changed, 0 insertions, 0 deletions