[#97086] [Ruby master Bug#16612] Enumerator::ArithmeticSequence#last with float range produces incorrect value — muraken@...
Issue #16612 has been updated by mrkn (Kenta Murata).
4 messages
2020/02/07
[#97095] [PATCH] Modify shebang of libexec/y2racc and libexec/racc2y. — Wang Mingyu <wangmy@...>
change /usr/local/bin/ruby to /usr/bin/env ruby.
3 messages
2020/02/08
[#97307] [Ruby master Feature#16663] Add block or filtered forms of Kernel#caller to allow early bail-out — headius@...
Issue #16663 has been reported by headius (Charles Nutter).
29 messages
2020/02/28
[ruby-core:97284] [Ruby master Feature#16644] qualified const init (self::CONST1 = 1) should be allowed in methods
From:
matz@...
Date:
2020-02-27 07:11:43 UTC
List:
ruby-core #97284
Issue #16644 has been updated by matz (Yukihiro Matsumoto).
Use `const_set`. I'd rather make all const re-assignment error if compatibility does not matter.
Matz.
----------------------------------------
Feature #16644: qualified const init (self::CONST1 = 1) should be allowed in methods
https://bugs.ruby-lang.org/issues/16644#change-84401
* Author: bughit (bug hit)
* Status: Open
* Priority: Normal
----------------------------------------
```rb
module Mod1
def self.define_consts
const_set(:CONST1, :CONST1)
# this is actual const re-assignment but only a warning
const_set(:CONST1, :CONST1)
# this is const initialization but becomes an error
# because it looks like it could be re-assignment
# if actual const re-assignment is only a warning
# why is a possible const re-assignment (which might not be one), an error
self::CONST2 = :CONST2 unless const_defined?(:CONST2, false)
end
define_consts
end
```
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>