[#86787] [Ruby trunk Feature#14723] [WIP] sleepy GC — ko1@...
Issue #14723 has been updated by ko1 (Koichi Sasada).
13 messages
2018/05/01
[#86790] Re: [Ruby trunk Feature#14723] [WIP] sleepy GC
— Eric Wong <normalperson@...>
2018/05/01
ko1@atdot.net wrote:
[#86791] Re: [Ruby trunk Feature#14723] [WIP] sleepy GC
— Koichi Sasada <ko1@...>
2018/05/01
On 2018/05/01 12:18, Eric Wong wrote:
[#86792] Re: [Ruby trunk Feature#14723] [WIP] sleepy GC
— Eric Wong <normalperson@...>
2018/05/01
Koichi Sasada <ko1@atdot.net> wrote:
[#86793] Re: [Ruby trunk Feature#14723] [WIP] sleepy GC
— Koichi Sasada <ko1@...>
2018/05/01
On 2018/05/01 12:47, Eric Wong wrote:
[#86794] Re: [Ruby trunk Feature#14723] [WIP] sleepy GC
— Eric Wong <normalperson@...>
2018/05/01
Koichi Sasada <ko1@atdot.net> wrote:
[#86814] Re: [Ruby trunk Feature#14723] [WIP] sleepy GC
— Koichi Sasada <ko1@...>
2018/05/02
[#86815] Re: [Ruby trunk Feature#14723] [WIP] sleepy GC
— Eric Wong <normalperson@...>
2018/05/02
Koichi Sasada <ko1@atdot.net> wrote:
[#86816] Re: [Ruby trunk Feature#14723] [WIP] sleepy GC
— Koichi Sasada <ko1@...>
2018/05/02
On 2018/05/02 11:49, Eric Wong wrote:
[#86847] [Ruby trunk Bug#14732] CGI.unescape returns different instance between Ruby 2.3 and 2.4 — me@...
Issue #14732 has been reported by jnchito (Junichi Ito).
3 messages
2018/05/02
[#86860] [Ruby trunk Feature#14723] [WIP] sleepy GC — sam.saffron@...
Issue #14723 has been updated by sam.saffron (Sam Saffron).
6 messages
2018/05/03
[#86862] Re: [Ruby trunk Feature#14723] [WIP] sleepy GC
— Eric Wong <normalperson@...>
2018/05/03
sam.saffron@gmail.com wrote:
[#86935] [Ruby trunk Bug#14742] Deadlock when autoloading different constants in the same file from multiple threads — elkenny@...
Issue #14742 has been reported by eugeneius (Eugene Kenny).
5 messages
2018/05/08
[#87030] [Ruby trunk Feature#14757] [PATCH] thread_pthread.c: enable thread caceh by default — normalperson@...
Issue #14757 has been reported by normalperson (Eric Wong).
4 messages
2018/05/15
[#87093] [Ruby trunk Feature#14767] [PATCH] gc.c: use monotonic counters for objspace_malloc_increase — ko1@...
Issue #14767 has been updated by ko1 (Koichi Sasada).
3 messages
2018/05/17
[#87095] [Ruby trunk Feature#14767] [PATCH] gc.c: use monotonic counters for objspace_malloc_increase — ko1@...
Issue #14767 has been updated by ko1 (Koichi Sasada).
9 messages
2018/05/17
[#87096] Re: [Ruby trunk Feature#14767] [PATCH] gc.c: use monotonic counters for objspace_malloc_increase
— Eric Wong <normalperson@...>
2018/05/17
ko1@atdot.net wrote:
[#87166] Re: [Ruby trunk Feature#14767] [PATCH] gc.c: use monotonic counters for objspace_malloc_increase
— Eric Wong <normalperson@...>
2018/05/18
Eric Wong <normalperson@yhbt.net> wrote:
[#87486] Re: [Ruby trunk Feature#14767] [PATCH] gc.c: use monotonic counters for objspace_malloc_increase
— Eric Wong <normalperson@...>
2018/06/13
I wrote:
[ruby-core:86789] Re: [Ruby trunk Bug#14350] Strange behavior for Array.min in ruby 2.5.0
From:
Austin Ziegler <halostatue@...>
Date:
2018-05-01 03:00:09 UTC
List:
ruby-core #86789
If float results are required for proper comparison (and I vaguely remember a similar `[[x, 0.0].max, 1.0].min` from pdf-writer), then force a float: `[[x.to_f, 0.0].max, 1.0].min`. On Fri, Apr 27, 2018 at 10:40 AM <alex@pointlessone.org> wrote: > Issue #14350 has been updated by cheba (Alexander Mankuta). > > > This change afects PrawnPDF gems (I'm a maintainer). > > From the maths point of view it is indeed insignificant, but there are > other areas where exact value matters. For example, in Prawn these values > are serialized. Integer `1` is serialized to a 1-byte string `"1"` and > Float `1.0` is serialized to 3-byte string `"1.0"`. While in the context of > PDF there's no difference between the values we don't want to change > generated documents. PDF is hard to inspect for changes because it's > essentially a binary format and a relatively complex one. Most our users > rely on binary stability of output for caching purposes and we strive to > make the output stable. > > With this change we can not provide the stability between Ruby versions. > We use it in our test suite among other things. > > ---------------------------------------- > Bug #14350: Strange behavior for Array.min in ruby 2.5.0 > https://bugs.ruby-lang.org/issues/14350#change-71681 > > * Author: artofhuman (Semyon Pupkov) > * Status: Closed > * Priority: Normal > * Assignee: > * Target version: > * ruby -v: 2.5.0 > * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN > ---------------------------------------- > 2.4.2 > > ~~~ ruby > [[1, 0.0].max, 1.0].min > > => 1 > ~~~ > > 2.5.0 > > ~~~ ruby > [[1, 0.0].max, 1.0].min > > => 1.0 > > [[1, 0.0].max, 1.0] > > => [1, 1.0] > > [1, 1.0].min > > => 1 > ~~~ > > I think it`s regression for ruby 2.5.0 > > > > -- > https://bugs.ruby-lang.org/ > > Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> > <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core> > -- Austin Ziegler 窶「 halostatue@gmail.com 窶「 austin@halostatue.ca http://www.halostatue.ca/ 窶「 http://twitter.com/halostatue Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>