From: takashikkbn@... Date: 2018-12-29T07:04:16+00:00 Subject: [ruby-core:90792] [Ruby trunk Bug#15478][Assigned] [RFC] erb: remove deprecation warnings from ERB.new Issue #15478 has been updated by k0kubun (Takashi Kokubun). Status changed from Third Party's Issue to Assigned > Why change existing behavior at all? That's because leaving a legacy code might confuse those who read the code and decreases the maintainability. I like to keep implementation simple so that we don't lose the speed of implementing new features. Otherwise Ruby implementation will stop evolving in the future for maintaining unnecessary legacy stuffs. That's why I'm pushing unnecessary things towards removal. However, > We can support both old and new-style kwargs without much overhead. this will become even more valid especially when we have real keyword arguments (I forgot the ticket number), even while we would not pass Hash as safe_level. As my opinion is not such stronger than you, I'll revert my change for decreasing the warn level from 2 to 1 in Ruby 2.7 and make the behavior the same as Ruby 2.6, believing that warn level 2 would not annoy non programmers. ---------------------------------------- Bug #15478: [RFC] erb: remove deprecation warnings from ERB.new https://bugs.ruby-lang.org/issues/15478#change-75968 * Author: normalperson (Eric Wong) * Status: Assigned * Priority: Normal * Assignee: k0kubun (Takashi Kokubun) * Target version: * ruby -v: * Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN ---------------------------------------- erb: remove deprecation warnings from ERB.new There's too much code relying on the old ordering; so any deprecation or removal of the old way is too annoying and only serves to make users angry. ---Files-------------------------------- 0001-erb-remove-deprecation-warnings-from-ERB.new.patch (2.87 KB) olddoc-erb-ruby26.patch (510 Bytes) -- https://bugs.ruby-lang.org/ Unsubscribe: