tiegz (Tieg Zaharia)
- Login: tiegz
- Email: tieg.zaharia@gmail.com
- Registered on: 04/04/2014
- Last sign in: 11/20/2015
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 1 | 0 | 1 |
Activity
11/18/2015
-
07:28 PM Ruby Feature #11710: [PATCH] Replace Set#merge with Set#merge! and make Set#merge non-mutating.
- (updating patch with a better change to the | method)
-
05:16 PM Ruby Feature #11710 (Assigned): [PATCH] Replace Set#merge with Set#merge! and make Set#merge non-mutating.
- The Set#merge method currently mutates its caller. I propose changing its behavior to non-mutating, and replace its current behavior with a mutating Set#merge! method.
For example, the current behavior:
```
> s = Set.new [1,2,3] ...
05/04/2014
-
06:31 PM Ruby Bug #9657: Segfault in bigdecimal/util.rb Float#to_d
- Thanks chikanagasan and wanabesan!
04/13/2014
-
10:25 PM Ruby Bug #9657: Segfault in bigdecimal/util.rb Float#to_d
- Ah, thanks Dieter, didn't think about that!
04/09/2014
-
10:32 PM Ruby Bug #9657: Segfault in bigdecimal/util.rb Float#to_d
- It seems like the fix might not make it out until 2.2.
If anyone runs into this while on 2.1, I was able to stop the segfaults by using BigDecimal coercion instead of to_d (`BigDecimal_coerce` has the GC guard). If you're using the m...
04/04/2014
-
07:39 PM Ruby Bug #9657: Segfault in bigdecimal/util.rb Float#to_d
- Same thing happening here a few times a day while calling to_d. Same line: bigdecimal/util.rb:18. Rails 3.2.17 and 2.1.1p76.