summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2021-06-30Prevent "warning: ambiguity between regexp and two divisions"Yusuke Endoh
2021-06-30[ruby/error_highlight] Bump versionYusuke Endoh
https://github.com/ruby/error_highlight/commit/8d483c251e
2021-06-30[ruby/error_highlight] Reconsider the API of ErrorHighlight.spotYusuke Endoh
https://github.com/ruby/error_highlight/commit/acb2046a82
2021-06-30[ruby/error_highlight] Experimentally support a custom formatterYusuke Endoh
https://github.com/ruby/error_highlight/commit/f40a1de20e
2021-06-30[ruby/error_highlight] Add some commentsYusuke Endoh
https://github.com/ruby/error_highlight/commit/e0c90c72c3
2021-06-30tool/sync_default_gems.rb: remove unneeded code for error_highlight syncYusuke Endoh
2021-06-30tool/sync_default_gems.rb: Add error_highlight gemYusuke Endoh
2021-06-30Use Module#ancestors order in recursive constant lookupAlan Wu
Before this commit, const_get with inherit=true and constant lookup expressions searched the ancestors of the starting point in an order different from `starting_point.ancestors`. Items in the ancestry list introduced through prepend were searched after searching the module they were prepended into. This oddity allowed for situations where constant lookups gave different results even though `starting_point.ancestors` is the same. Do the lookup in the same order as `starting_point.ancestors` by skipping classes and modules that have an origin iclass. The origin iclass is in the super chain after the prepended modules. Note that just like before this commit, the starting point of the constant lookup is always the first item that we search, regardless of the presence of any prepended modules. [Bug #17887] Notes: Merged: https://github.com/ruby/ruby/pull/4585
2021-06-30* 2021-06-30 [ci skip]git
2021-06-30Specify version to remove as bare numbersNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/3972
2021-06-30Ensure that version number starts with digitsNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/3972
2021-06-30Show the removal versionNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/3972
2021-06-30rb_warn_deprecated_to_remove_at [Feature #17432]Nobuyoshi Nakada
At compilation time with RUBY_DEBUG enabled, check if the removal version has been reached. Notes: Merged: https://github.com/ruby/ruby/pull/3972
2021-06-29tool/test-bundled-gems.rb: Stop tests conflicting with error_highlightYusuke Endoh
This hack should be removed after the minitest side is updated. https://github.com/seattlerb/minitest/pull/880 Notes: Merged: https://github.com/ruby/ruby/pull/4586
2021-06-29Rename error_squiggle to error_highlightYusuke Endoh
Notes: Merged: https://github.com/ruby/ruby/pull/4586
2021-06-29[WIP] add error_squiggle gemYusuke Endoh
``` $ ./local/bin/ruby -e '1.time {}' -e:1:in `<main>': undefined method `time' for 1:Integer (NoMethodError) 1.time {} ^^^^^ Did you mean? times ``` https://bugs.ruby-lang.org/issues/17930 Notes: Merged: https://github.com/ruby/ruby/pull/4586
2021-06-29Fix crash on RGENGC_CHECK_MODE=4Peter Zhu
When running btest there is a crash when compiled with RGENGC_CHECK_MODE=4. The crash happens because `during_gc` is not turned off before `gc_marks_check` is called, causing the marking to happen on the main mark stack instead of mark stack created in `objspace_allrefs`. Notes: Merged: https://github.com/ruby/ruby/pull/4610
2021-06-29Add basic test for updated IO wait functions.Samuel Williams
Notes: Merged: https://github.com/ruby/ruby/pull/4612
2021-06-29Use assert_not_match "Did you mean?" for UncorrectableNameCheckTestYusuke Endoh
... instead of exact matching. I'm now creating a built-in gem that modifies Exception's error message, so the expectation value is changed. IMO, it is good to check that did_you_mean suggestion is NOT added in the uncorrectable case. https://github.com/ruby/did_you_mean/commit/ebe88ec4d2
2021-06-29Use String#include? instead of end_with? to avoid message duplicationYusuke Endoh
Previously, did_you_mean used `msg.end_with?(suggestion)` to check if its suggestion is already added. I'm now creating a gem that also modifies Exception's message. This breaks did_you_mean's duplication check. This change makes the check use String#include? instead of end_with?. https://github.com/ruby/did_you_mean/commit/b35e030549
2021-06-29Let Correctable#original_message skip prepended method definitionsYusuke Endoh
Previously, DidYouMean::Correctable#original_message did `method(:to_s).super_method.call` to call the original to_s method by skipping Correctable#to_s. I'm now creating a gem that prepends another to_s method to NameError, which confuses the hack. An immediate solution is to replace it with `method(:to_s).super_method.super_method.call` to skip the two methods. But it is too ad-hoc. This changeset uses more extensible approach and allow a prepended module to declare that they should be skipped by defining a constant named `SKIP_TO_S_FOR_SUPER_LOOKUP`. https://github.com/ruby/did_you_mean/commit/8352c154e3
2021-06-29Should require "rbconfig" to use RbConfigNobuyoshi Nakada
https://github.com/ruby/did_you_mean/commit/fbe5aaaae8
2021-06-29Start v1.6.0 developmentYuki Nishijima
https://github.com/ruby/did_you_mean/commit/3f69171813
2021-06-29Prefer qualified names under ThreadNobuyoshi Nakada
2021-06-29* 2021-06-29 [ci skip]git
2021-06-28Avoid `free(3)`ing invalid pointerxtkoba
Fixes [Bug #17794] Notes: Merged: https://github.com/ruby/ruby/pull/4611
2021-06-28Refined define_thread_classNobuyoshi Nakada
Reduce duplications * ID caluculations of the same name * checks against the same name * registration to the root module hash
2021-06-28* 2021-06-28 [ci skip]git
2021-06-28Share freeze option handlingNobuyoshi Nakada
2021-06-27Show leaked file descriptors only, without cwd, txt, and so onNobuyoshi Nakada
2021-06-27Narrow the tracing of object allocations to during each testNobuyoshi Nakada
2021-06-27Check if closed after each yield [Bug #17661]Nobuyoshi Nakada
2021-06-27[ruby/irb] Optimize show_source command furtherTakashi Kokubun
https://github.com/ruby/irb/pull/249 actually slowed down how `code` is concatenated. The original way of creating `code` is faster. [before] user system total real 2.420137 0.005364 2.425501 ( 2.426264) [after] user system total real 1.000221 0.007454 1.007675 ( 1.008295) Theoretically, this implementation might skip lines that don't appear in Ripper tokens, but this assumes such lines don't impact whether the code passes compilation or not. At least normal blank lines seem to have an `on_ignored_nl` token anyway though. https://github.com/ruby/irb/commit/27dd2867cd
2021-06-27[ruby/irb] Improve performance of `show_source` for large classMasataka Pocke Kuwabara
https://github.com/ruby/irb/commit/2b79e9ad21
2021-06-27Added macros for days in monthNobuyoshi Nakada
2021-06-27Shrink monthly tablesNobuyoshi Nakada
2021-06-27* 2021-06-27 [ci skip]git
2021-06-26Work around issue transcoding issue with non-ASCII compatible encodings and ↵Jeremy Evans
xml escaping When using a non-ASCII compatible source and destination encoding and xml escaping (the :xml option to String#encode), the resulting string was broken, as it used the correct non-ASCII compatible encoding, but contained data that was ASCII-compatible instead of compatible with the string's encoding. Work around this issue by detecting the case where both the source and destination encoding are non-ASCII compatible, and transcoding the source string from the non-ASCII compatible encoding to UTF-8. The xml escaping code will correctly handle the UTF-8 source string and the return the correctly encoded and escaped value. Fixes [Bug #12052] Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org> Notes: Merged: https://github.com/ruby/ruby/pull/4605 Merged-By: jeremyevans <code@jeremyevans.net>
2021-06-26Scan the coderange in the given encodingNobuyoshi Nakada
2021-06-26Disable RBIMPL_ATTR_DEPRECATED for Coverity Scan buildYusuke Endoh
Coverity Scan emulates gcc but seems not to support this attribute correctly.
2021-06-26* 2021-06-26 [ci skip]git
2021-06-26iseq.c: Make ast_line_count return 0 when syntax error occurredYusuke Endoh
This broke coverage CI ``` 1) Failure: TestRequire#test_load_syntax_error [/home/runner/work/actions/actions/ruby/test/ruby/test_require.rb:228]: Exception(SyntaxError) with message matches to /unexpected/. [SyntaxError] exception expected, not #<TypeError: no implicit conversion of false into Integer>. ``` https://github.com/ruby/actions/runs/2914743968?check_suite_focus=true
2021-06-25Revert "Revert "[ruby/reline] Fix failed test""aycabta
I'm so sorry, the previous revert was just a mistake. This reverts commit 9103c3ba8bc09f287f69ca322f58faa34e003f2e.
2021-06-25Revert "[ruby/reline] Fix failed test"aycabta
This reverts commit 491591c7cee842601118efc2698e0e41283827b3.
2021-06-25[ruby/reline] Fix missing require.Samuel Williams
https://github.com/ruby/reline/commit/010b28dfe9
2021-06-25[ruby/reline] Avoid using blocking `IO.select`.Samuel Williams
https://github.com/ruby/reline/commit/de94746393
2021-06-25[ruby/reline] Fix failed testima1zumi
For ruby/ruby repository's AppVeyor CI (Windows environment), `Reline::IOGate.encoding` will be changed from `UTF-8` to `Windows-31J` after the test is run. So, when `test/reline/test_key_actor_emacs.rb` is loaded, `Reline::IOGate.encoding == Encoding::UTF_8` will be `true`, but at the time of test execution, `Reline::IOGate.encoding` is `Windows-31J`. For this reason, I changed the test method to check `Reline::IOGate.encoding` in the test method. https://github.com/ruby/reline/commit/10e1ce3320
2021-06-25Followed up 66d2fc7989d741bf5a73286233139901cecb4fc2Hiroshi SHIBATA
2021-06-25[ruby/racc] Remove Object monkey patchAaron Patterson
I don't think we need this monkey patch anymore, so lets remove it! https://github.com/ruby/racc/commit/464485e912
2021-06-25[ruby/racc] Removed needless condition for old versions of RubyGems.Hiroshi SHIBATA
https://github.com/ruby/racc/commit/fe3183b1ff
generated by cgit v1.2.3 (git 2.25.1) at 2026-05-15 18:45:51 +0000