| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/irb/pull/575)
* Support native integration with ruby/debug
* Prevent using multi-irb and activating debugger at the same time
Multi-irb makes a few assumptions:
- IRB will manage all threads that host sub-irb sessions
- All IRB sessions will be run on the threads created by IRB itself
However, when using the debugger these assumptions are broken:
- `debug` will freeze ALL threads when it suspends the session (e.g. when
hitting a breakpoint, or performing step-debugging).
- Since the irb-debug integration runs IRB as the debugger's interface,
it will be run on the debugger's thread, which is not managed by IRB.
So we should prevent the 2 features from being used at the same time.
To do that, we check if the other feature is already activated when
executing the commands that would activate the other feature.
https://github.com/ruby/irb/commit/d8fb3246be
|
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/irb/pull/681)
It shouldn't be `RubyLex`'s responsibility to handle IO. So this moves
the configuration to `IRB::Irb`.
https://github.com/ruby/irb/commit/daff750076
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/irb/pull/680)
The `rescue` was removed at https://github.com/ruby/irb/commit/420e7d227011.
https://github.com/ruby/irb/commit/8fa688e9c0
|
|
|
|
|
|
| |
Do not add directories which would let chkbuild fires accidentally, to
just under `test`. The "fixtures" directory is often used to place
test stuffs.
|
|
|
|
| |
Chkbuild fires accidentally on `test/fixtures` directory.
|
|
|
|
|
| |
Chkbuild runs for each directories just under `test` directory when
`test-all` failed. `test/excludes` itself should not be a target.
|
|
|
|
|
|
| |
In general, if the same option specifying a single value is given
multiple times at the same level, the last one overrides the earlier
ones, unless prohibited.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
INF_RUBY prompt
(https://github.com/ruby/irb/pull/679)
* Drop showing indent level number in DEFAULT prompt and INF_RUBY prompt
* Update prompt part of test_rendering's expected result
https://github.com/ruby/irb/commit/3847532e54
|
|
|
|
|
|
|
|
|
|
|
| |
StdioInputMethod
(https://github.com/ruby/irb/pull/671)
They are both built on top of stdio and are basically extended version
of StdioInputMethod. They also share several attributes and methods with
StdioInputMethod.
https://github.com/ruby/irb/commit/c5f5abdbde
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
It's the actual cfp[6] in the default build, so it's confusing to say
otherwise in the comment.
|
| |
|
| |
|
|
|
|
| |
https://github.com/ruby/ruby/actions/runs/5836610844/job/15830549311
|
| |
|
|
|
|
|
|
|
| |
check_code_state
(https://github.com/ruby/irb/pull/678)
https://github.com/ruby/irb/commit/4a6af7d1ed
|
|
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/irb/pull/670)
Since assignment check relies on tokenization with `Ripper`, it feels like
the responsibility of `RubyLex`. `Irb#eval_input` should simply get the result
when calling `each_top_level_statement` on `RubyLex`.
https://github.com/ruby/irb/commit/89d1adb3fd
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/irb/pull/677)
We already skipped history integration tests in core CI in #675 due to
suspicion on nested IRB sessions don't work on certain operating systems.
But after #669, the evaluation integration test also started to fail on
some Core CI suites. So, it looks like the integration test setup may not
work in Core CI, at least in some suites.
Consider `ruby/irb` already has rather sophisticated test suite, I think
it's better to skip the integration tests in core CI for now.
https://github.com/ruby/irb/commit/6f49b4c108
|
| |
|
|
|
|
|
|
|
| |
semicolon
(https://github.com/ruby/irb/pull/669)
https://github.com/ruby/irb/commit/50185c2833
|
|
|
|
|
|
| |
(https://github.com/ruby/irb/pull/676)
https://github.com/ruby/irb/commit/a2763acade
|
|
|
|
|
|
|
|
|
|
|
| |
* YJIT: implement codegen for rb_int_lshift
* Update yjit/src/asm/x86_64/mod.rs
Co-authored-by: Takashi Kokubun <takashikkbn@gmail.com>
---------
Co-authored-by: Takashi Kokubun <takashikkbn@gmail.com>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
`$(MAINLIBS)` should include `$(LIBS)` already.
|
| |
|
|
|
|
|
| |
`YJIT_BINDGEN_DIFF_OPTS=--exit-code make yjit-bindgen` is not the same
as `make yjit-bindgen YJIT_BINDGEN_DIFF_OPTS=--exit-code`, of course.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/zlib/pull/55)
zstream_discard_input was encoding and character-aware when given input is user-provided, so this discards `len` chars instead of `len` bytes.
Also Zlib.gunzip explains in its rdoc that it is equivalent with the following code, but this doesn't fail for UTF-8 String.
```ruby
string = %w[1f8b0800c28000000003cb48cdc9c9070086a6103605000000].pack("H*").force_encoding('UTF-8')
sio = StringIO.new(string)
p gz.read #=> "hello"
gz&.close
p Zlib.gunzip(string) #=> Zlib::DataError
```
Reported and discovered by eagletmt at https://twitter.com/eagletmt/status/1689692467929694209
https://github.com/ruby/zlib/commit/c5e58bc62a
|