Issue #21681 has been updated by dmitry.pogrebnoy (Dmitry Pogrebnoy). Thank you for the detailed explanation! That clears things up a lot. Wishing Ruby Box a smooth landing in Ruby 4.0. Really looking forward to seeing how it evolves. ---------------------------------------- Misc #21681: Clarification on the Status and Roadmap of Ruby Box for Ruby 4.0 https://bugs.ruby-lang.org/issues/21681#change-115185 * Author: dmitry.pogrebnoy (Dmitry Pogrebnoy) * Status: Open ---------------------------------------- Hello! I’d like to ask about the expected state of Ruby Box in the upcoming Ruby 4.0 release. I came across the roadmap here: https://bugs.ruby-lang.org/versions/105, which mentions the related feature: https://bugs.ruby-lang.org/issues/21311. From the discussion, it seems there are several concerns around the proposal. I also noticed that the name Ruby Box originated from this thread: https://bugs.ruby-lang.org/issues/21385. In that discussion, it was mentioned that Ruby Box is expected to serve as a low-level API. However, I haven’t found any information about a potential high-level API built on top of it. Since I’d like to plan ahead and ensure that development tools can support this new feature and its adoption, could you please clarify: * Given the threads mentioned above, what is the final vision/scope of the Ruby Box feature? I appreciate if you point me towards relevant documentation. * Is Ruby Box expected to be included by default in Ruby 4.0 (as usual planned for late December if I got it right)? * What is the general plan or roadmap for Ruby Box? Are there any intentions to introduce a high-level API or additional related features? Thank you very much for your time and for any insights you can share. -- https://bugs.ruby-lang.org/