[#104481] [Ruby master Feature#18020] Introduce `IO::Buffer` for fiber scheduler. — samuel@...

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

31 messages 2021/07/03

[#104492] [Ruby master Bug#18022] Spec errors for rbconfig/unicode_[emoji_]version_spec: Using Ruby 2.7 even when on Ruby 3.1 — duerst@...

Issue #18022 has been reported by duerst (Martin Dst).

8 messages 2021/07/04

[#104552] [Ruby master Feature#18033] Time.new to parse a string — nobu@...

Issue #18033 has been reported by nobu (Nobuyoshi Nakada).

26 messages 2021/07/09

[#104560] [Ruby master Bug#18035] Introduce general module for immutable by default. — samuel@...

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

41 messages 2021/07/09

[#104629] [Ruby master Misc#18039] DevelopersMeeting20210819Japan — mame@...

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

11 messages 2021/07/16

[#104643] [Ruby master Bug#18040] Why should `foo(1 if true)` be an error? — bughit.github@...

Issue #18040 has been reported by bughit (bug hit).

10 messages 2021/07/19

[#104665] [Ruby master Feature#18042] YARV code optimization — motoroller95@...

Issue #18042 has been reported by motoroller (Iskandar Gohar).

11 messages 2021/07/23

[#104692] [Ruby master Bug#18048] Thread#join can break with fiber scheduler unblock fails or blocks. — samuel@...

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

10 messages 2021/07/27

[#104723] [Ruby master Bug#18054] No rule to make target 'thread_fd_close.c', needed by 'thread_fd_close.o' — duerst@...

Issue #18054 has been reported by duerst (Martin Dst).

8 messages 2021/07/29

[ruby-core:104729] [Ruby master Feature#18055] Introduce

From: shalokshalom@...
Date: 2021-07-30 09:30:30 UTC
List: ruby-core #104729
Issue #18055 has been updated by shalokshalom (Matthias Schuster).


Hi Matz!

I see value in it, since it gives us one unified way, to call libraries:

Where ever you do it, when ever you do it, it is always the most optimal choice.

Currently, users shy away from using autoload, since its riddled with use cases, in which it can bite your back.

This gives a nice 'wrapper' around autoload and require, that lets us use always the most optimal of the two.

It can encourage, to load libraries only, when they are really used, and by that, increasing the start-up time.

I hope this can help :)

----------------------------------------
Feature #18055: Introduce
https://bugs.ruby-lang.org/issues/18055#change-93063

* Author: shalokshalom (Matthias Schuster)
* Status: Open
* Priority: Normal
----------------------------------------
Currently, ``autoload`` provides the ability to load libraries on the fly, also called lazy loading, in order to avoid huge startup times.

This has some disadvantages, who already lead nearly to its [discontinuation](https://bugs.ruby-lang.org/issues/5653)

I suggest a proposal, that solves both these issues.

``introduce``

I imagine this keyword, respectively method behaves like ```require``` at the top of the file and does act like ```autoload``` within a definition.

We can also introduce exceptions for cases like the above linked threads.

Its also a nice guideline, and easy to remember.

*Summary*: ``introduce`` can always behave predictable, optimal, and even work fine without the programmer knowing about its implementation. 


Similar issues: 
 - https://bugs.ruby-lang.org/issues/15592



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

In This Thread

Prev Next