[#114348] [Ruby master Feature#19832] Method#destructive?, UnboundMethod#destructive? — "sawa (Tsuyoshi Sawada) via ruby-core" <ruby-core@...>

Issue #19832 has been reported by sawa (Tsuyoshi Sawada).

15 messages 2023/08/06

[#114365] [Ruby master Bug#19834] Segmentation fault while running in docker — "ramachandran@... (Ramachandran A) via ruby-core" <ruby-core@...>

Issue #19834 has been reported by ramachandran@mallow-tech.com (Ramachandran A).

7 messages 2023/08/09

[#114380] [Ruby master Bug#19837] Concurrent calls to Process.waitpid2 misbehave on Ruby 3.1 & 3.2 — "kjtsanaktsidis (KJ Tsanaktsidis) via ruby-core" <ruby-core@...>

Issue #19837 has been reported by kjtsanaktsidis (KJ Tsanaktsidis).

7 messages 2023/08/11

[#114399] [Ruby master Feature#19839] Need a method to check if two ranges overlap — "shouichi (Shouichi KAMIYA) via ruby-core" <ruby-core@...>

Issue #19839 has been reported by shouichi (Shouichi KAMIYA).

27 messages 2023/08/18

[#114410] [Ruby master Bug#19841] Marshal.dump stack overflow with recursive Time — "segiddins (Samuel Giddins) via ruby-core" <ruby-core@...>

Issue #19841 has been reported by segiddins (Samuel Giddins).

9 messages 2023/08/18

[#114422] [Ruby master Feature#19842] Intorduce M:N threads — "ko1 (Koichi Sasada) via ruby-core" <ruby-core@...>

Issue #19842 has been reported by ko1 (Koichi Sasada).

30 messages 2023/08/21

[#114590] [Ruby master Bug#19857] Eval coverage is reset after each `eval`. — "ioquatix (Samuel Williams) via ruby-core" <ruby-core@...>

Issue #19857 has been reported by ioquatix (Samuel Williams).

21 messages 2023/08/30

[ruby-core:114450] [Ruby master Bug#10416] Create mechanism for updating of Unicode data files downstreams when we want

From: "jeremyevans0 (Jeremy Evans) via ruby-core" <ruby-core@...>
Date: 2023-08-22 21:58:40 UTC
List: ruby-core #114450
Issue #10416 has been updated by jeremyevans0 (Jeremy Evans).





@duerst Do you think this can be closed?



----------------------------------------

Bug #10416: Create mechanism for updating of Unicode data files downstreams=
 when we want

https://bugs.ruby-lang.org/issues/10416#change-104209



* Author: duerst (Martin D=FCrst)

* Status: Open

* Priority: Normal

* Assignee: nobu (Nobuyoshi Nakada)

* ruby -v: ruby 2.2.0dev (2014-10-22 trunk 48092) [x86_64-cygwin]

* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN

----------------------------------------

The current mechanism for updating Unicode data files will create the follo=
wing problem:

Downstream compilers/packagers will download Unicode data files ONE time (t=
hey may already have done so).



However, if they don't activate ALWAYS_UPDATE_UNICODE =3D yes, these files =
will never get updated, and they will stay on Unicode version 7.0 even if i=
n five years Unicode is e.g. on version 12.0.

On the other hand, if they activate ALWAYS_UPDATE_UNICODE =3D yes (and assu=
ming issue #10415 gets fixed), they constantly update to the latest version=
 of Unicode. That's good for those who actually want this, but now what our=
 current policy is.

What's missing is that we (Ruby core) can make sure downstream checkouts up=
date to a new Unicode version when we want then to do so (as we e.g. can do=
 for other parts that are based on Unicode data, see e.g. https://bugs.ruby=
-lang.org/issues/9092), without sending an email to everybody and hoping th=
ey read and follow it.



[Currently, the only solution I know will work is the one pointed out by Yu=
i Naruse in https://bugs.ruby-lang.org/issues/10084#note-17, but I'm okay w=
ith any other solution.]













--=20

https://bugs.ruby-lang.org/

 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-c=
ore.ml.ruby-lang.org/

In This Thread

Prev Next