Issue #19866 has been updated by Eregon (Benoit Daloze). From https://bugs.ruby-lang.org/issues/19883#change-104825
Seems odd for a standard library to attempt to load a non-standard library first, and fallback to loading a standard library.
Agreed. I think either lib/readline.rb should only use reline and not try readline-ext, or lib/readline.rb should be deprecated/warn, and users then adapt to `require 'readline-ext'`/`require 'reline'` ---------------------------------------- Bug #19866: Future of `readline.rb` https://bugs.ruby-lang.org/issues/19866#change-104831 * Author: vo.x (Vit Ondruch) * Status: Open * Priority: Normal * ruby -v: ruby 3.3.0dev (2023-09-05 master 7c8932365f) [x86_64-linux] * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- I wonder what is the future of readline.rb? It still tries to load `readline.so` by default. Is this intended behavior? I'd say that instead, it should rather fire a deprecation warning and load reline. Or maybe the whole readline gem should be completely removed? -- https://bugs.ruby-lang.org/