Thank you for all the valuable input. We have investigated opinions about the keyword argument pain points very carefully, and concluded the biggest one is the overwhelming deprecations warnings regarding keyword arguments from 2.7.
So our planning actions will be:
- stop noisy warnings regarding keyword arguments (in 2.7.2)
- encourage use of
warning
gem from Jeremy. By using the gem, you can cause warnings (as it does now), or get the 3.0 behavior right now. - we will move on to the new keyword argument behavior in Ruby3.0 as planned, that will be released on December this year.
- we are still considering some issues, e.g. retrieving given arguments altogether. But we need some time.
If you have any questions or concerns, feel free to post here.
Matz.