urbanautomaton (Simon Coffey)
- Login: urbanautomaton
- Registered on: 03/14/2017
- Last sign in: 09/08/2021
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 1 | 1 |
Activity
09/08/2021
-
10:58 AM Ruby Bug #18155: (nil..nil).cover?(x) is true for all x since beginless ranges were introduced
- I should add: if we don't want to raise an error, then out of options 1 and 2 my preference would be for 2, as saying a beginless-and-endless range has no type seems more persuasive to me.
-
09:37 AM Ruby Bug #18155 (Closed): (nil..nil).cover?(x) is true for all x since beginless ranges were introduced
- ### Description
The introduction of beginless ranges in #14799 changed the behaviour of `Range#cover?` when both the beginning and the end of a `Range` are `nil`. Previously such a range would cover no values; now it covers all values...
03/14/2017
-
11:55 PM Ruby Misc #13283: Disable `&' interpreted as argument prefix warning when passing symbol to Enumerable#map
- mojavelinux (Dan Allen) wrote:
> The alternative, a bitwise operation on a symbol, makes little sense. That's especially when the bitwise operator is directly adjacent to the symbol.
Bitwise AND isn't the only interpretation of infix...