| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Co-authored-by: ryannevell (Ryan Nevell) <ryan.nevell@gmail.com>
|
|
|
|
|
|
| |
because it was for TestColorPrinter
https://github.com/ruby/irb/commit/7569206fd4
|
|
|
|
| |
https://github.com/ruby/irb/commit/eea9c16804
|
|
|
|
| |
https://github.com/ruby/irb/commit/d95e8daab3
|
|
|
|
| |
https://github.com/ruby/erb/commit/cb59f11ec8
|
| |
|
|
|
|
|
| |
After setting ruby2_keywords for bmethod, the rest of arguments
had been ignored. [Bug #17558]
|
|
|
|
|
|
| |
http://ci.rvm.jp/logfiles/brlog.trunk-random1.20210119-074232
https://github.com/ruby/irb/commit/ea87592d4a
|
|
|
|
| |
https://github.com/ruby/irb/commit/8e9e6c4037
|
|
|
|
| |
https://github.com/ruby/irb/commit/6663057083
|
| |
|
|
|
|
|
|
|
|
| |
http://rubyci.s3.amazonaws.com/ubuntu2004/ruby-master/log/20210119T033003Z.log.html.gz
```
/home/chkbuild/chkbuild/tmp/build/20210119T033003Z/ruby/test/ruby/test_jit.rb:781:
warning: -e:5: warning: possibly useless use of -@ in void context
```
|
|
|
|
|
|
|
|
| |
http://rubyci.s3.amazonaws.com/ubuntu2004/ruby-master/log/20210119T033003Z.log.html.gz
```
/home/chkbuild/chkbuild/tmp/build/20210119T033003Z/ruby/test/ruby/test_pattern_matching.rb:798:
warning: assigned but unused variable - x
```
|
|
|
|
|
|
|
|
|
| |
Peephole optimization doesn't play well with find pattern at
least. The only case when a pattern matching could have
unreachable patterns is when we have lasgn/dasgn node, which
shouldn't happen in real-life.
Fixes https://bugs.ruby-lang.org/issues/17534
|
|
|
|
| |
forgotten in https://github.com/ruby/ruby/pull/4018
|
|
|
|
|
|
| |
* due to the difference of backtrace pointed out by @aycabta
https://github.com/ruby/irb/commit/5e00a0ae61
|
|
|
|
| |
https://github.com/ruby/irb/commit/fcf6b34bc5
|
|
|
|
| |
https://github.com/ruby/irb/commit/a6a33d908f
|
|
|
|
| |
https://github.com/ruby/reline/commit/53ff2b09c7
|
|
|
|
|
|
| |
Because of chdir, log files ware created in temporary directries on Windows.
https://github.com/ruby/reline/commit/200b469a68
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Warn Struct#initialize with only keyword args
A part of [Feature #16806]
* Do not warn if `keyword_init: false`
is explicitly specified
* Add a NEWS entry
* s/in/from/
* Make sure all fields are initialized
|
| |
|
|
|
|
| |
https://github.com/ruby/bigdecimal/commit/1cb92487f7
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in receiver
Previously, if a class included a module and then prepended the
same module, the prepend had no effect. This changes the behavior
so that the prepend has an effect unless the module is already
prepended the receiver.
While here, rename the origin_seen variable in include_modules_at,
since it is misleading. The variable tracks whether c has been seen,
not whether the origin of klass has been.
Fixes [Bug #17423]
|
|
|
|
|
|
|
|
| |
because the name "MJIT" is an internal code name, it's inconsistent with
--jit while they are related to each other, and I want to discourage future
JIT implementation-specific (e.g. MJIT-specific) APIs by this rename.
[Feature #17490]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Callinfo was being written in to an array and the GC would not see the
reference on the stack. `new_insn_send` creates a new callinfo object,
then it calls `new_insn_core`. `new_insn_core` allocates a new INSN
linked list item, which can end up calling `xmalloc` which will trigger
a GC:
https://github.com/ruby/ruby/blob/70cd351c7c71c48ee18d7c01e851a89614086f8f/compile.c#L968-L969
Since the callinfo object isn't on the stack, the GC won't see it, and
it can get collected. This patch just refactors `new_insn_send` to keep
the object on the stack
Co-authored-by: John Hawthorn <john@hawthorn.email>
|
| |
|
|
|
|
| |
[Feature #17485]
|
| |
|
|
|
|
|
|
| |
They should be affected, as well as `$VERBOSE`, by `-w`/`-W`
options, not only in the main script but in scripts loaded by `-r`
option too.
|
|
|
|
|
|
| |
This reverts commit fac2498e0299f13dffe4f09a7dd7657fb49bf643 for
now, due to [Bug #17509], the breakage in the case `super` is
called in `respond_to?`.
|
| |
|
|
|
|
| |
[Fixes ruby/ostruct#23]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using dtoa of mode=0, we can determine the number of digits in decimal that is
necessary to represent the given Float number without errors.
This change permits digits=0 in BigDecimal(flt) and Float#to_d, and these
methods use dtoa of mode=0 when the given digits is 0.
Internal implicit conversion from Float also uses digits=0.
[Fix GH-70]
https://github.com/ruby/bigdecimal/commit/2dbe170e35
|
| |
|
|
|
|
| |
https://github.com/ruby/bigdecimal/commit/95c201f2d3
|
|
|
|
|
| |
https://github.com/ruby/bigdecimal/commit/d163f170a4
https://github.com/ruby/bigdecimal/commit/ff8eeeb064
|
|
|
|
|
|
| |
This fixes ruby/reline#246.
https://github.com/ruby/reline/commit/07a73ba601
|
|
|
|
|
|
|
| |
The current line was being handled incorrectly when displaying the hit
history, so it has been fixed to be correct.
https://github.com/ruby/reline/commit/a3df4343b3
|
| |
|
|
|
|
| |
Co-authored-by: Jeremy Evans <code@jeremyevans.net>
|
|
|
|
| |
https://bugs.ruby-lang.org/issues/17485#change-89871
|
| |
|
| |
|
|
|
|
| |
Not to interfere in other tests.
|
|
|
|
| |
https://github.com/ruby/bigdecimal/commit/28d3836366
|
|
|
|
| |
refs: 733ed1e184
|
|
|
|
|
|
|
|
|
| |
The incompatible interface is not helpful, again if you want to use it
as a standalone library, falling it back to PP.
Original PP.pp also ends with `out << "\n"`.
https://github.com/ruby/irb/commit/4c74c7d84c
|