Skip to content

Ruby 4 support #55

Description

@pldavid2

@dblock are you planning to rename the gem being ruby 4 has Ruby namespace reserved ?
Thank you

Activity

  1. dblock commented on Feb 20, 2026

    @dblock
    Owner

    I could, what shall we call this? I'd appreciate a PR for the change, please?

  2. added a commit that references this issue on Aug 15, 2026
    187ab8e
  3. dblock commented on Aug 15, 2026

    @dblock
    Owner

    Please see #57.

  4. dblock commented on Aug 15, 2026

    @dblock
    Owner

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions