| CARVIEW |
Select Language
HTTP/2 200
cache-control: max-age=0, private, must-revalidate
content-type: text/html; charset=utf-8
etag: W/"1ccf41240e24713fe68186818865ad86"
nel: {"report_to":"heroku-nel","response_headers":["Via"],"max_age":3600,"success_fraction":0.01,"failure_fraction":0.1}
referrer-policy: strict-origin-when-cross-origin
report-to: {"group":"heroku-nel","endpoints":[{"url":"https://nel.heroku.com/reports?s=FJdNHxrQtnAttVetZtIrSgUnlN5ISvmCzcp8NJ6TWRE%3D\u0026sid=e11707d5-02a7-43ef-b45e-2cf4d2036f7d\u0026ts=1753388833"}],"max_age":3600}
reporting-endpoints: heroku-nel="https://nel.heroku.com/reports?s=FJdNHxrQtnAttVetZtIrSgUnlN5ISvmCzcp8NJ6TWRE%3D&sid=e11707d5-02a7-43ef-b45e-2cf4d2036f7d&ts=1753388833"
server: Heroku
set-cookie: _redmine_session=QkRLUW5sSmlBbUFUakVVdUthM1Y5N3dGME5ZSHNPWjR2SmRHbDBaQ0xBbG1abTl4V0xpZytlWnBkNS9BdzI0ajViOEZSNFdGdTJuZVo2dGMxU3JPaW9aK3ZvZEJUWkl6S29Fd3l5alV3N0FMZ3FyQm1xMy9pMXFvZ2ZhcXg4bVMzaGtQTUhtOTlVeTBaek5XOWRqaER3T0RsektnY3hNRno0SFM4a1A4ZEJGeEJabXcybHRUbVpZbG5hN3g2MDJsLS00bk5BeHFRNCtnVHdDZ3c5SEppSm9nPT0%3D--c468436d80b6e79aefdd8ee1eee5c6a18cf511db; path=/; secure; httponly; samesite=lax
strict-transport-security: max-age=63072000; includeSubDomains
vary: Accept
via: 2.0 heroku-router
x-content-type-options: nosniff
x-download-options: noopen
x-frame-options: SAMEORIGIN
x-permitted-cross-domain-policies: none
x-request-id: d4480f24-6a69-7aa8-b86b-f73883aea6b1
x-runtime: 0.100096
x-xss-protection: 1; mode=block
content-length: 24343
date: Thu, 24 Jul 2025 20:27:13 GMT
Bug #21402: ruby2_keywords affects methods/procs with post arguments - Ruby - Ruby Issue Tracking System
Project
General
Profile
Tags
Custom queries
Actions
Bug #21402
open
ruby2_keywords affects methods/procs with post arguments
Added by jeremyevans0 (Jeremy Evans) about 1 month ago.
Description
I believe this is an oversight. We forgot to consider post arguments during the development of ruby2_keywords. I believe we should not allow ruby2_keywords on methods/procs with post arguments. Example:
def a(*c, **kw) [c, kw] end
def b(*a, b) a(*a, b) end
ruby2_keywords(:b)
b({foo: 1}, bar: 1)
# Currently: [[{foo: 1}], {bar: 1}]
# Expected: [[{foo: 1}, {bar: 1}], {}]
I think the current behavior is unexpected and undesired, because instead of flagging the last element in the splat array, it flags a post argument.
I've submitted a pull request to fix this: https://github.com/ruby/ruby/pull/13475
No data to display
Actions
Like0
Powered by Redmine © 2006-2025 Jean-Philippe Lang
Loading...