ruby.git/lib/irb/completion.rb, branch v3_2_11

[ruby/irb] Fix https://github.com/ruby/irb/pull/295: Ignore Java

2022-11-17T03:39:04+00:00

package reference objects in
JRuby

https://github.com/ruby/irb/commit/84d030182d

[ruby/irb] Don't lazily retrieve gem specs for completion

2022-11-07T14:44:25+00:00

There are a few downsides of the current approach:

1. Because gem specs are lazily retrieved, this computation happens in
   every irb completion test case, which is not necessary. (In tests we
   don't cache the result of `retrieve_files_to_require_from_load_path`)
2. Gem::Specification.latest_specs is sensible to the content of
   LOAD_PATH. And when combined with 1, tests fail "randomly" if they
   try to mutate LOAD_PATH, even though the test subject it's something
   else.

So by pre-computing and storing the gem paths in a constant, it guarantees
that the computation only happens once and it doesn't get affected by test
cases.

One argument could be made against the change is that, it'll store
unnecessary data for users that disable autocompletion. But the
counter-arguments are:

1. Since autocompletion is enabled by default, this should not be the
   case for most users.
2. For users with autocompletion enabled, IRB already caches the
   result of `retrieve_files_to_require_from_load_path` in memory, which
   should have a similar size of GEM_SPECS. And we currently haven't
   received any report about problems caused by such memory consumption.

https://github.com/ruby/irb/commit/c671d39020

[ruby/irb] Sort constant completion's candidates

2022-10-07T18:17:42+00:00

https://github.com/ruby/irb/commit/ee9b33c817

[ruby/irb] Lazily evaluate candidates locals

2022-10-07T18:17:42+00:00

https://github.com/ruby/irb/commit/19a2fcbd87

[ruby/irb] Fixed sort of variables in completion

2022-10-05T10:22:13+00:00

https://github.com/ruby/irb/commit/5842888255

[ruby/irb] Change to explicit method call in completion (https://github.com/ruby/irb/pull/369)

2022-10-02T21:55:53+00:00

Ensure that methods are called even when local variables are defined.
see: https://github.com/ruby/irb/issues/368

https://github.com/ruby/irb/commit/c34d54b8bb

[ruby/irb] Handle non-String $LOAD_PATH values more carefully

2022-09-21T13:24:27+00:00

In addition to String values, $LOAD_PATH can also take objects that
respond_to the `to_path` method, like Pathname objects. So `irb` should
be able to handle those objects too.

And if $LOAD_PATH contains objects that can't be converted into String,
`irb` should simply ignore it.

https://github.com/ruby/irb/commit/b2f562176b

[ruby/irb] Ignore parenthesis during completion

2021-10-12T21:33:48+00:00

Rename method

https://github.com/ruby/irb/commit/619aecb412

[ruby/irb] Revert "Show original string byte sequence to debug"

2021-09-24T14:50:32+00:00

This reverts commit b42fe5937ab2a605a198ffb866db5ccda541568d.

https://github.com/ruby/irb/commit/b22094a16f

[ruby/irb] Show original string byte sequence to debug

2021-09-24T14:50:26+00:00

https://github.com/ruby/irb/commit/7a97bb0e56