You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ruby master has now copied all the methods Puma used from io/wait to IO. I originally started the PR for that, as io/wait won't need to be required for Ruby 3.2 and later. I.think. I haven't tested it yet, but I think the only methods used in Puma are wait_readable and wait_writable...
The text was updated successfully, but these errors were encountered:
I interpreted #2381 to mean that all ruby files could be loaded with require_relative, but any *.so files needed to be loaded with require. We only have one puma_http11.
We could use require_relative, and if an error is raised, load via require...
Have a branch prepared for a PR, so I thought I'd ask first.
Any reason to not change all
require
statements torequire_relative
?See https://github.com/ruby/ruby/search?q=require_relative, and #2381
Ruby master has now copied all the methods Puma used from
io/wait
toIO
. I originally started the PR for that, asio/wait
won't need to be required for Ruby 3.2 and later. I.think. I haven't tested it yet, but I think the only methods used in Puma arewait_readable
andwait_writable
...The text was updated successfully, but these errors were encountered: