aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* * 2021-07-01 [ci skip]git2021-07-011-2/+2
|
* Use stride passed into os_obj_of_iPeter Zhu2021-06-301-3/+2
|
* [ruby/irb] Rescue a specific errorTakashi Kokubun2021-06-301-1/+1
| | | | | | Rescuing StandardError is prone to bugs caused by a typo or obsoleted methods. https://github.com/ruby/irb/commit/eb5260fcd5
* [ruby/irb] Fix error on `ls object_cant_define_singleton`Masataka Pocke Kuwabara2021-06-302-2/+22
| | | | | | such as `ls 42`, `ls :sym` and so on https://github.com/ruby/irb/commit/b1d436a853
* "nodoc" needs to exclude "doc" [ci skip]Nobuyoshi Nakada2021-06-301-1/+1
|
* [ruby/error_highlight] Allow the development version (= master branch) of ↵Yusuke Endoh2021-06-301-1/+1
| | | | | | Ruby 3.1 https://github.com/ruby/error_highlight/commit/2dca1446c9
* [DOC] add notes and examples for pipe [ci skip]Nobuyoshi Nakada2021-06-301-7/+19
|
* Add the gemspec for error_highlightYusuke Endoh2021-06-301-0/+27
|
* Prevent "warning: ambiguity between regexp and two divisions"Yusuke Endoh2021-06-301-1/+1
|
* [ruby/error_highlight] Bump versionYusuke Endoh2021-06-301-1/+1
| | | | https://github.com/ruby/error_highlight/commit/8d483c251e
* [ruby/error_highlight] Reconsider the API of ErrorHighlight.spotYusuke Endoh2021-06-302-18/+16
| | | | https://github.com/ruby/error_highlight/commit/acb2046a82
* [ruby/error_highlight] Experimentally support a custom formatterYusuke Endoh2021-06-304-28/+74
| | | | https://github.com/ruby/error_highlight/commit/f40a1de20e
* [ruby/error_highlight] Add some commentsYusuke Endoh2021-06-301-1/+5
| | | | https://github.com/ruby/error_highlight/commit/e0c90c72c3
* tool/sync_default_gems.rb: remove unneeded code for error_highlight syncYusuke Endoh2021-06-301-1/+0
|
* tool/sync_default_gems.rb: Add error_highlight gemYusuke Endoh2021-06-301-0/+7
|
* Use Module#ancestors order in recursive constant lookupAlan Wu2021-06-302-5/+74
| | | | | | | | | | | | | | | | | | | | | 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]
* * 2021-06-30 [ci skip]git2021-06-301-1/+1
|
* Specify version to remove as bare numbersNobuyoshi Nakada2021-06-305-15/+15
|
* Ensure that version number starts with digitsNobuyoshi Nakada2021-06-301-1/+2
|
* Show the removal versionNobuyoshi Nakada2021-06-302-8/+10
|
* rb_warn_deprecated_to_remove_at [Feature #17432]Nobuyoshi Nakada2021-06-305-27/+85
| | | | | At compilation time with RUBY_DEBUG enabled, check if the removal version has been reached.
* tool/test-bundled-gems.rb: Stop tests conflicting with error_highlightYusuke Endoh2021-06-291-0/+6
| | | | | This hack should be removed after the minitest side is updated. https://github.com/seattlerb/minitest/pull/880
* Rename error_squiggle to error_highlightYusuke Endoh2021-06-298-33/+33
|
* [WIP] add error_squiggle gemYusuke Endoh2021-06-2914-8/+1503
| | | | | | | | | | | | | ``` $ ./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
* Fix crash on RGENGC_CHECK_MODE=4Peter Zhu2021-06-291-0/+2
| | | | | | | | 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`.
* Add basic test for updated IO wait functions.Samuel Williams2021-06-295-49/+401
|
* Use assert_not_match "Did you mean?" for UncorrectableNameCheckTestYusuke Endoh2021-06-291-1/+1
| | | | | | | | | | ... 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
* Use String#include? instead of end_with? to avoid message duplicationYusuke Endoh2021-06-291-1/+1
| | | | | | | | | | | 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
* Let Correctable#original_message skip prepended method definitionsYusuke Endoh2021-06-291-1/+8
| | | | | | | | | | | | | | | | | 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
* Should require "rbconfig" to use RbConfigNobuyoshi Nakada2021-06-291-0/+1
| | | | https://github.com/ruby/did_you_mean/commit/fbe5aaaae8
* Start v1.6.0 developmentYuki Nishijima2021-06-291-1/+1
| | | | https://github.com/ruby/did_you_mean/commit/3f69171813
* Prefer qualified names under ThreadNobuyoshi Nakada2021-06-2923-179/+181
|
* * 2021-06-29 [ci skip]git2021-06-291-1/+1
|
* Avoid `free(3)`ing invalid pointerxtkoba2021-06-281-0/+2
| | | Fixes [Bug #17794]
* Refined define_thread_classNobuyoshi Nakada2021-06-281-4/+4
| | | | | | | Reduce duplications * ID caluculations of the same name * checks against the same name * registration to the root module hash
* * 2021-06-28 [ci skip]git2021-06-281-1/+1
|
* Share freeze option handlingNobuyoshi Nakada2021-06-283-24/+11
|
* Show leaked file descriptors only, without cwd, txt, and so onNobuyoshi Nakada2021-06-271-1/+1
|
* Narrow the tracing of object allocations to during each testNobuyoshi Nakada2021-06-271-25/+25
|
* Check if closed after each yield [Bug #17661]Nobuyoshi Nakada2021-06-272-1/+39
|
* [ruby/irb] Optimize show_source command furtherTakashi Kokubun2021-06-271-1/+4
| | | | | | | | | | | | | | | | | | | | 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
* [ruby/irb] Improve performance of `show_source` for large classMasataka Pocke Kuwabara2021-06-271-4/+11
| | | | https://github.com/ruby/irb/commit/2b79e9ad21
* Added macros for days in monthNobuyoshi Nakada2021-06-271-13/+8
|
* Shrink monthly tablesNobuyoshi Nakada2021-06-271-6/+6
|
* * 2021-06-27 [ci skip]git2021-06-271-1/+1
|
* Work around issue transcoding issue with non-ASCII compatible encodings and ↵Jeremy Evans2021-06-262-0/+25
| | | | | | | | | | | | | | | | | | | | 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>
* Scan the coderange in the given encodingNobuyoshi Nakada2021-06-263-9/+46
|
* Disable RBIMPL_ATTR_DEPRECATED for Coverity Scan buildYusuke Endoh2021-06-261-1/+5
| | | | | Coverity Scan emulates gcc but seems not to support this attribute correctly.
* * 2021-06-26 [ci skip]git2021-06-261-1/+1
|
* iseq.c: Make ast_line_count return 0 when syntax error occurredYusuke Endoh2021-06-261-0/+4
| | | | | | | | | | | | 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
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-02 20:27:59 +0000