| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
```
% docker run -it --rm rubylang/all-ruby env ALL_RUBY_SINCE=ruby-2.6 ./all-ruby -e 'root = RubyVM::AbstractSyntaxTree.parse("x = 1 + 2")
p [root, root.type]
call = root.children[2]
p [call, call.type]
'
ruby-2.6.0 [#<RubyVM::AbstractSyntaxTree::Node:SCOPE@1:0-1:9>, :SCOPE]
[#<RubyVM::AbstractSyntaxTree::Node:LASGN@1:0-1:9>, :LASGN]
...
ruby-2.7.0 [#<RubyVM::AbstractSyntaxTree::Node:SCOPE@1:0-1:9>, :SCOPE]
[#<RubyVM::AbstractSyntaxTree::Node:LASGN@1:0-1:9>, :LASGN]
```
|
| |
|
| |
|
|
|
|
|
| |
It is considered a mistake, because calling this method with no
arguments has no effect.
|
| |
|
|
|
|
| |
to /projects/ruby-master
|
|
|
|
| |
trunk branch was deleted.
|
|
|
|
| |
The format is the same as Travis / AppVeyor now.
|
|
|
|
|
| |
Similar to 4fb6643f31cdee33184043ce17c42001274c4392.
This is motivated by the lack of the same feature in GitHub Actions.
|
|
|
|
|
| |
When `make all` fails, we should not run tests and output of such run is
confusing.
|
| |
|
|
|
|
|
|
| |
[ruby-core:93516][Feature #15982]
https://github.com/ruby/racc/pull/123
|
|
|
|
| |
https://github.com/bundler/bundler/commit/29d932d72d
|
|
|
|
| |
`make check` runs test -> test-all -> test-spec, and other CIs follow that too.
|
|
|
|
| |
We're actually using it for PR :p
|
| |
|
| |
|
| |
|
|
|
|
| |
https://github.com/ruby/irb/commit/1f3a84ab6b
|
| |
|
|
|
|
|
| |
- Generated by [npx github-actions-badge](https://github.com/azu/github-actions-badge)
- Add MJIT
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The set_auto_indent method calculates the correct number of spaces for
indenting a line. We think there might be a few bugs in this method so
we are testing the current functionality to make sure nothing breaks
when we address those bugs.
Example test failure:
```
1) Failure:
TestIRB::TestRubyLex#test_auto_indent [/Users/Ben/Projects/irb/test/irb/test_ruby_lex.rb:75]:
Calculated the wrong number of spaces for:
def each_top_level_statement
initialize_input
catch(:TERM_INPUT) do
loop do
begin
prompt
unless l = lex
throw :TERM_INPUT if @line == ''
else
.
<10> expected but was
<12>.
```
https://github.com/ruby/irb/commit/752d5597ab
|
|
|
|
|
|
|
|
| |
unknown
This is a workaround for https://github.com/ruby/irb/issues/50
https://github.com/ruby/reline/commit/5725677d1a
|
|
|
|
|
|
| |
* bignum.h: Add BIGNUM_EMBED_P
* bignum.c: Use macros for handling BIGNUM_EMBED_FLAG
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
`NoMethodError` has been raised instead of `FrozenError`.
|
|
|
|
| |
It died again https://github.com/ruby/ruby/runs/368837347
|
|
|
|
|
| |
Starting from ruby 2.7.0, there's no longer a connection between the hexadecimal
number that #inspect shows and the object's ID.
|
| |
|
| |
|
|
|
|
| |
Minitest has the released tags now.
|
|
|
| |
TestRelineAsReadline#test_input_metachar passes on MinGW
|
|
|
|
|
| |
The phrase "[doing X] is now warned" is not grammatically correct in
English as it is lacking an object. We can make these sentences read
better by switching to "[doing X] will now display a warning" instead.
|
| |
|
| |
|
|
|
|
| |
like "{platform} / make ({make target}, ...)"
|
| |
|
|
|
|
| |
in favor of #2791
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* MinGW - skip spec in spec/ruby/optional/capi/thread_spec.rb
C-API Thread function rb_thread_call_without_gvl
-- runs a C function with the global lock unlocked and unlocks IO with the generic RUBY_UBF_IO
stops/freezes spec tests
See https://bugs.ruby-lang.org/issues/16265
* MinGW - skip test test/resolv/test_dns.rb
Test times out in CI (both AppVeyor & Actions), cannot repo locally
* MinGW - skip test test/ruby/test_thread_queue.rb
* Add Actions mingw.yml
|
|
|
|
|
|
|
|
| |
This reverts commit 75e8dd58f69c190c9698d0133942032903fb2f07.
We seem to randomly hit another issue these days:
https://github.com/ruby/ruby/runs/368756135
https://github.com/ruby/ruby/runs/368756191
|
|
|
|
|
| |
Needed for `UNALIGNED_MEMBER_ACCESS` using `COMPILER_WARNING_`*
macros.
|
|
|
|
| |
[Bug #16406]
|
| |
|
|
|
|
|
|
| |
* Deciding lambdaness of (f << g) using g
* Use version guards for spec changes
|