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
Here's my strong opinion loosely held. Ruby 4.0 only reserves the top-level Ruby module for its own constants (Ruby::VERSION, Ruby::Box, etc.), it doesn't prevent gems from reopening/extending the module. Since we only define Ruby::Enum (not Ruby itself), there's no actual conflict, so the rename isn't necessary. If Ruby were to introduce Ruby::Enum, we would definitely rename. Closing this in the meantime.
@dblock are you planning to rename the gem being ruby 4 has Ruby namespace reserved ?
Thank you