Please sign in to comment.
Remove coercion of octal, binary, hex for Integer properties
* This extra behavior is probably unecessary and would be little used. In addition it would cause "0123" to be treated as 83 rather than 123, which I think is probably more expected to anyone familiar with how String#to_i works. It's only really the Kernel::Integer() method that treats "0123" as an octal, and it's in far less frequent use than String#to_i. If specific octal, binary or hex coercion is necessary then I would probably suggest using a custom type rather than an Integer property. I am removing this for now, since if I'm wrong it will be easy to add back in, but it would be really difficult to remove behavior like this after a release.
- Loading branch information...
Showing with 1 addition and 23 deletions.