{"action":"created","issue":{"url":"https://api.github.com/repos/rubinius/rubinius/issues/3382","labels_url":"https://api.github.com/repos/rubinius/rubinius/issues/3382/labels{/name}","comments_url":"https://api.github.com/repos/rubinius/rubinius/issues/3382/comments","events_url":"https://api.github.com/repos/rubinius/rubinius/issues/3382/events","html_url":"https://github.com/rubinius/rubinius/issues/3382","id":71446532,"number":3382,"title":"NameError: wrong constant name BIG∞","user":{"login":"fny","id":346068,"avatar_url":"https://avatars.githubusercontent.com/u/346068?v=3","gravatar_id":"","url":"https://api.github.com/users/fny","html_url":"https://github.com/fny","followers_url":"https://api.github.com/users/fny/followers","following_url":"https://api.github.com/users/fny/following{/other_user}","gists_url":"https://api.github.com/users/fny/gists{/gist_id}","starred_url":"https://api.github.com/users/fny/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fny/subscriptions","organizations_url":"https://api.github.com/users/fny/orgs","repos_url":"https://api.github.com/users/fny/repos","events_url":"https://api.github.com/users/fny/events{/privacy}","received_events_url":"https://api.github.com/users/fny/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-04-28T01:17:57Z","updated_at":"2015-04-28T01:34:35Z","closed_at":null,"body":"`BIG∞ = BigDecimal::INFINITY` is perfectly valid in Ruby 1.9.3+ but doesn't work in Rubinius. :cry: \r\n"},"comment":{"url":"https://api.github.com/repos/rubinius/rubinius/issues/comments/96871216","html_url":"https://github.com/rubinius/rubinius/issues/3382#issuecomment-96871216","issue_url":"https://api.github.com/repos/rubinius/rubinius/issues/3382","id":96871216,"user":{"login":"jemc","id":4623870,"avatar_url":"https://avatars.githubusercontent.com/u/4623870?v=3","gravatar_id":"","url":"https://api.github.com/users/jemc","html_url":"https://github.com/jemc","followers_url":"https://api.github.com/users/jemc/followers","following_url":"https://api.github.com/users/jemc/following{/other_user}","gists_url":"https://api.github.com/users/jemc/gists{/gist_id}","starred_url":"https://api.github.com/users/jemc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jemc/subscriptions","organizations_url":"https://api.github.com/users/jemc/orgs","repos_url":"https://api.github.com/users/jemc/repos","events_url":"https://api.github.com/users/jemc/events{/privacy}","received_events_url":"https://api.github.com/users/jemc/received_events","type":"User","site_admin":false},"created_at":"2015-04-28T01:34:35Z","updated_at":"2015-04-28T01:34:35Z","body":"It's rather obnoxious that [the Symbol-validation logic for this in Rubinius is written in C++](https://github.com/rubinius/rubinius/blob/6ce75ef91493f4df1a192ea4e5429aadc04fed13/vm/symbol_table.cpp#L19-L27), when as far as I can tell it is not *really* an integral part of the VM.\r\n\r\nIf you want a quick workaround, you can do something like:\r\n```ruby\r\nclass Symbol\r\n  def is_constant?\r\n    true\r\n  end\r\nend\r\n```\r\n\r\nThat will allow any symbol to be used in a `const_get` or `const_set`.  Obviously, it would be better in the long run to improve the Symbol validator logic (probably starting by moving it to Ruby if possible)."}}