[#113756] [Ruby master Bug#19711] NoMethodError "private method `new' called for class" since bebd05fb51ea65bc57344b67100748200f8311eb — "yahonda (Yasuo Honda) via ruby-core" <ruby-core@...>

Issue #19711 has been reported by yahonda (Yasuo Honda).

7 messages 2023/06/05

[#113771] [Ruby master Feature#19712] IO#reopen removes singleton class — "itarato (Peter Arato) via ruby-core" <ruby-core@...>

Issue #19712 has been reported by itarato (Peter Arato).

11 messages 2023/06/05

[#113782] [Ruby master Bug#19716] SystemStackError occurs too easily on Alpine Linux (due to small stack size reported by pthread_attr_getstacksize on musl libc) — "alexdowad (Alex Dowad) via ruby-core" <ruby-core@...>

Issue #19716 has been reported by alexdowad (Alex Dowad).

6 messages 2023/06/07

[#113788] [Ruby master Bug#19717] `ConditionVariable#signal` is not fair when the wakeup is consistently spurious. — "ioquatix (Samuel Williams) via ruby-core" <ruby-core@...>

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

13 messages 2023/06/07

[#113819] [Ruby master Feature#19720] Warning for non-linear Regexps — "Eregon (Benoit Daloze) via ruby-core" <ruby-core@...>

Issue #19720 has been reported by Eregon (Benoit Daloze).

11 messages 2023/06/08

[#113835] [Ruby master Misc#19722] DevMeeting-2023-07-13 — "mame (Yusuke Endoh) via ruby-core" <ruby-core@...>

Issue #19722 has been reported by mame (Yusuke Endoh).

9 messages 2023/06/09

[#113944] [Ruby master Feature#19737] Add `IO::Buffer#cat` for concat `IO::Buffer` instances — "unasuke (Yusuke Nakamura) via ruby-core" <ruby-core@...>

Issue #19737 has been reported by unasuke (Yusuke Nakamura).

7 messages 2023/06/19

[#113953] [Ruby master Bug#19739] Key cannot be found in a Hash when slice! method is applied to the key — "ilya.andreyuk (Ilya Andreyuk) via ruby-core" <ruby-core@...>

Issue #19739 has been reported by ilya.andreyuk (Ilya Andreyuk).

9 messages 2023/06/20

[#113966] [Ruby master Bug#19742] Introduce `Module#anonymous?` — "ioquatix (Samuel Williams) via ruby-core" <ruby-core@...>

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

47 messages 2023/06/21

[#114025] [Ruby master Feature#19744] Namespace on read — "tagomoris (Satoshi TAGOMORI) via ruby-core" <ruby-core@...>

Issue #19744 has been reported by tagomoris (Satoshi TAGOMORI).

71 messages 2023/06/27

[#114032] [Ruby master Misc#19747] Propose Kevin Newton and Jemma Issroff as core committers — "k0kubun (Takashi Kokubun) via ruby-core" <ruby-core@...>

Issue #19747 has been reported by k0kubun (Takashi Kokubun).

8 messages 2023/06/28

[#114038] [Ruby master Bug#19749] Confirm correct behaviour when attaching private method with `#define_method` — "itarato (Peter Arato) via ruby-core" <ruby-core@...>

Issue #19749 has been reported by itarato (Peter Arato).

15 messages 2023/06/28

[ruby-core:113750] [Ruby master Misc#19693] Data initialization is significantly slower than Struct

From: janosch-x via ruby-core <ruby-core@...>
Date: 2023-06-03 11:13:12 UTC
List: ruby-core #113750
Issue #19693 has been updated by janosch-x (Janosch M=FCller).





@byroot



nice idea! i've [tried it](https://gist.github.com/jaynetics/0d04eb85177140=
e2a84fc88aeea68764). it still doubles (instead of triples) kw init speed, a=
t the cost of halving speed when initializing with list args:



```

           orig list:  7136048.0 i/s

          patch list:  3115468.7 i/s - 2.29x  slower

            patch kw:  2956280.5 i/s - 2.41x  slower

             orig kw:  1621000.3 i/s - 4.40x  slower

```





> I'm not sure is spec compliant, as it would allow to call Foo.new("a", a:=
 "also_a")



i think this one test, for structs with `keyword_init: true`, will fail: ht=
tps://github.com/ruby/ruby/blame/master/test/ruby/test_struct.rb#L116



however, this gives me the idea that a simple Ruby keyword initializer (`de=
f self.new(a: nil, b: nil); orig_new(a, b) end`) could be auto-defined, and=
 speed tripled, if and only if `keyword_init: true` is given. this should b=
e spec compliant. structs with `keyword_init: true` already raise an arity =
error when given list args.=20



then again, i assume the idea is to rather fade out the `keyword_init` opti=
on, which doesn't even exist for `Data`?







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

Misc #19693: Data initialization is significantly slower than Struct

https://bugs.ruby-lang.org/issues/19693#change-103397



* Author: janosch-x (Janosch M=FCller)

* Status: Closed

* Priority: Normal

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

Maybe there is potential to make it as fast as Struct?



```ruby

require 'benchmark/ips'



S =3D Struct.new(:a, :b, :c, :d, :e, :f, :g, :h, :i, :j)

D =3D Data.define(:a, :b, :c, :d, :e, :f, :g, :h, :i, :j)



Benchmark.ips do |x|

  x.report('Struct') { S.new(1, 2, 3, 4, 5, 6, 7, 8, 9, 10) }

  x.report('Data')   { D.new(1, 2, 3, 4, 5, 6, 7, 8, 9, 10) }

  x.compare!

end; 1



# =3D> [...]

# =3D>             Struct:  6916530.4 i/s

# =3D>               Data:  1507259.5 i/s - 4.59x  slower

```







--=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