summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Added release option to sync only released version of the default gemsHEADmasterHiroshi SHIBATA2022-03-08-5/+18
|
* test/io/console/test_io_console.rb: parens neededYusuke Endoh2022-03-08-1/+1
|
* Skip three tests on FreeBSD 13Yusuke Endoh2022-03-08-1/+26
| | | | | | Some tests that use signals frequently fail randomly on FreeBSD 13. Maybe something around signals has changed in FreeBSD 13. This change skips them tentatively.
* [DOC] Enhanced RDoc for String #tr and #tr! (#5626)Burdette Lamar2022-03-07-27/+41
|
* * 2022-03-08 [ci skip]git2022-03-08-1/+1
|
* [rubygems/rubygems] Add newline to validate_platforms! message when platform ↵Alex Gittemeier2022-03-08-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | is missing When I run bundle install with BUNDLE_DEPLOYMENT=true in the environment on a different platform than I usually do development, I get the following output to the console (wrapped exactly as shown): Your bundle only supports platforms ["x86_64-darwin-19"] but your local platform is x86_64-linux. Add the current platform to the lockfile with `bundle lock --add-platform x86_64-linux` and try again. Because the way the message wraps, its not as simple as copying the suggested command to the clipboard because it contains a newline: $ bundle lock Writing lockfile to [...]/Gemfile.lock $ --add-platform x86_64-linux Adding a newline right before the command forces the command in the error message to be on the same line, which facilitates copy-pasting the command in the message. https://github.com/rubygems/rubygems/commit/4cf6989b11
* Use rb_ary_unshare for shared array in rb_ary_replacePeter Zhu2022-03-07-7/+1
| | | | | rb_ary_unshare will perform FL_UNSET_SHARED and rb_ary_decrement_share.
* [DOC] Fix documentation typo for Process#clock_gettimeThierry Joyal2022-03-07-1/+1
| | | | Fixes [Misc #18610]
* Update default gems list at 9c531ca524506f9de7bc4643fd6d89 [ci skip]git2022-03-07-0/+1
|
* [ruby/ostruct] Drop unused directives from gemspec ↵Olle Jonsson2022-03-07-2/+0
| | | | | | | | (https://github.com/ruby/ostruct/pull/39) This gem exposes no executables. https://github.com/ruby/ostruct/commit/a1242f7ebe
* [ruby/ostruct] v0.5.3Marc-André Lafortune2022-03-07-1/+1
| | | | https://github.com/ruby/ostruct/commit/322efd0e61
* [ruby/ostruct] Fix class and method as attribute namesLadislav Gallay2022-03-07-1/+7
| | | | https://github.com/ruby/ostruct/commit/7258535073
* [DOC] Change to guidance on lists in What's Here section (#5618)Burdette Lamar2022-03-07-10/+11
| | | Currently, the guide says a "What's Here" section should have a labeled list for the methods. Such a list can render very differently in different browsers, and are often erratic in their indentation of continuation lines.
* * 2022-03-07 [ci skip]git2022-03-07-1/+1
|
* [rubygems/rubygems] Update README.md.ttBrad Gessler2022-03-07-9/+3
| | | | | | Reduce the number of steps required to install a gem from two steps to one by using `bundle add` https://github.com/rubygems/rubygems/commit/2c968420cd
* * 2022-03-06 [ci skip]git2022-03-06-1/+1
|
* [rubygems/rubygems] Make `--strict` flag of `update` and `outdated` commands ↵David Rodríguez2022-03-06-61/+43
| | | | | | | | | | | | | consistent Previously they had slightly different behavior when combined with conservative updating flags. The correct behavior is the `--update-strict` option, so `--script` now does that, The `--update-strict` option is left there for now but I will deprecate it later. https://github.com/rubygems/rubygems/commit/ab42046229
* * 2022-03-05 [ci skip]git2022-03-05-1/+1
|
* Mention removed gems since 3.1 [ci skip]Kazuhiro NISHIYAMA2022-03-05-1/+4
|
* Remove gdbm related code from Travis CIKazuhiro NISHIYAMA2022-03-04-2/+0
| | | | | | The related extensions have been removed. Related: https://github.com/ruby/ruby/pull/4619
* sitelibdir makes no sense in ruby itselfNobuyoshi Nakada2022-03-04-0/+4
|
* Fix typos [ci skip]Kazuhiro NISHIYAMA2022-03-04-2/+2
|
* Dedup superclass array in leaf sibling classesJohn Hawthorn2022-03-03-24/+26
| | | | | | | | | | | | | | | | Previously, we would build a new `superclasses` array for each class, even though for all immediate subclasses of a class, the array is identical. This avoids duplicating the arrays on leaf classes (those without subclasses) by calculating and storing a "superclasses including self" array on a class when it's first inherited and sharing that among all superclasses. An additional trick used is that the "superclass array including self" is valid as "self"'s superclass array. It just has it's own class at the end. We can use this to avoid an extra pointer of storage and can use one bit of a flag to track that we've "upgraded" the array.
* * 2022-03-04 [ci skip]git2022-03-04-1/+1
|
* Doc: fix documentation typo for Array#minRogerio Bordignon2022-03-03-1/+1
|
* Update to ruby/spec@82cd3a3Benoit Daloze2022-03-03-72/+213
|
* Update to ruby/mspec@bd47c2aBenoit Daloze2022-03-03-14/+48
|
* Update default gems list at 7f7db124ee6a72ec178d4045387062 [ci skip]git2022-03-03-0/+1
|
* [ruby/cgi] Bump up v0.3.2Hiroshi SHIBATA2022-03-03-1/+1
| | | | https://github.com/ruby/cgi/commit/734dfdf1b4
* [DOC] mark `rb_str_init` as `:nodoc:`Nobuyoshi Nakada2022-03-03-0/+1
| | | | | Otherwise, an empty entry will be generated as `String::new` along with the one from doc/string.rb.
* [DOC] Rename doc/*.rb as doc/*.rdocNobuyoshi Nakada2022-03-03-0/+4
| | | | | With `:markup: ruby` directive so that they are parsed as ruby scripts.
* * 2022-03-03 [ci skip]git2022-03-03-1/+1
|
* [DOC] Addition to encoding.rdoc (#5617)Burdette Lamar2022-03-02-36/+40
| | | | | | | | Adds section "Transcoding a Stream," listing relevant methods in IO. Moves an example from section "String Encoding Example" to the new section. Removes header "String Encoding Example" for now-empty section. Changes items in section "Transcoding a String" from labeled list items to bullet list items. (Labeled list items are sometimes rendered with strange indentations for continued lines, and are always rendered with different indentations for the items.)
* [MSWin] Allow gems with VS2022 for VS2019 build ruby [Misc #18362]Nobuyoshi Nakada2022-03-02-1/+4
| | | | | Although not sure if it is really compatible, let’s give it a try.
* Exclude binstubs testsNobuyoshi Nakada2022-03-02-0/+4
| | | | | When relative loading is enabled, the executable ruby is expected installed at the same directory as the binstub.
* Revert "enc/depend: fix out-of-src build with --with-static-linked-ext" (#5616)Nobuyoshi Nakada2022-03-02-7/+1
| | | | This reverts commit 32ad8df9d1e07e1b2435a8890d070802fcd2989f, which broke out-of-src build with the pre-generated transcoder sources.
* vm_method.c: avoid signature mismatch in rb_f_notimplement callYuta Saito2022-03-02-3/+16
| | | | | | | | | | | | | | `rb_f_notimplement` has a similar signature with arity=-1, but it has an extra marker argument to distinguish it from other methods in compile-time type check in rb_define_method. This trick is introduced to override a given arity to be -1 since https://github.com/ruby/ruby/commit/9ef51b0b89a10c8c401cb9f2337e47a25be72cbe However, the trailing extra argument introduces a signature mismatch between caller and callee expectation. This patch adds rb_f_notimplement_internal, which has canonical arity=-1 signature, and makes rb_define_method family to inserts a method entry with rb_f_notimplement_internal instead of rb_f_notimplement.
* [ruby/rdoc] Use `Marshal.load io` instead of `Marshal.load io.read`Kazuhiro NISHIYAMA2022-03-02-4/+4
| | | | https://github.com/ruby/rdoc/commit/135198a31c
* dir.c: use self-made IFTODT in rb_pathtype_t if availableYuta Saito2022-03-02-2/+8
| | | | | | | | | | | | | | | | | | | dir.c defines IFTODT if the system doesn't have it. The macro is used when comparing with rb_pathtype_t's cases. rb_pathtype_t's cases are defined by DT_XXX macro if they are available, or defined using IFTODT. Most POSIX-compatible platforms have both IFTODT and DT_XXX and most of other platforms like MinGW have neither of them. On those platforms, DT_XXX-oriented rb_pathtype_t is always compared with values converted by system's IFTODT, and emulated-IFTODT-oriented rb_pathtype_t is always compared with values converted by emulated-IFTODT. However, when IFTODT is *not defined* and DT_XXX is *defined*, like on wasi-libc, DT_XXX-oriented rb_pathtype_t was compared with values converted by emulated-IFTODT, and they are not guaranteed to be compatible. This patch fixes such a situation by using emulated-IFTODT to define rb_pathtype_t when either IFTODT or DT_XXX is not available.
* enc/depend: fix out-of-src build with --with-static-linked-extYuta Saito2022-03-02-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When out-of-src build, at the beginning of a build, `make -f enc.mk srcs` generates trans C sources under build dir. On the other hand, enc/trans/*.o were built from trans C sources generated under srcdir due to the following auto-generated rules from enc/depend. ``` encsrcdir = ../src/enc ... enc/trans/big5.$(OBJEXT): $(encsrcdir)/trans/big5.c ``` Therefore, trans C sources are generated twice under srcdir and build dir during a build. Ideally, trans C sources have always been built before compilation of enc/trans/*.o because the source generation is prereq, so making enc/trans/*.o doesn't trigger trans C source generation and shouldn't require MINIRUBY as a make arg for enc.mk. However, the second trans C source gen is unintentionally triggered by enc/trans/*.o, so `make -f enc.mk libencs` requires MINIRUBY for now. When no `--with-static-linked-ext`, `make -f enc.mk libencs` is triggered from common.mk with MINIRUBY, so there is no problem. But when `--with-static-linked-ext`, libencs should be statically-linked to ruby, so `make -f enc.mk libencs` is triggered from exts.mk, and exts.mk invokes it without MINIRUBY. Therefore, when out-of-src build and with `--with-static-linked-ext`, the second trans C source gen fails due to missing MINIRUBY. This issue is deterministically reproducible without -j because common.mk's `main` rule also has libencs prerequisite. This patch supresses the second trans C source gen.
* Using macros to check iseq elementS.H2022-03-02-3/+3
|
* Wrap ruby_abi_version in `extern "C"` for C++Peter Zhu2022-03-01-0/+8
| | | | | Make ruby_abi_version have C linkage so that the symbol can be found in the shared object.
* Close files in examples in io.c (#5615)Burdette Lamar2022-03-01-0/+65
|
* [DOC] Add encoding external/internal example to encoding.rdoc (#5610)Burdette Lamar2022-03-01-0/+23
| | | | | | | | | | | | | * Add encoding external/internal example to encoding.rdoc * Add encoding external/internal example to encoding.rdoc * Update doc/encoding.rdoc I think there may be some more of these that I've recently put into io.c. Will check tomorrow and create new PR if so. Co-authored-by: Peter Zhu <peter@peterzhu.ca> Co-authored-by: Peter Zhu <peter@peterzhu.ca>
* Show embed status of array when len is 0 in objspace dumpPeter Zhu2022-03-01-1/+23
|
* * 2022-03-02 [ci skip]git2022-03-02-1/+1
|
* Fix race in TestThread#test_thread_status_in_trapBenoit Daloze2022-03-01-1/+1
| | | | | * If the sleep is not enough to run the rest of the logic the process would be exited early, e.g., before the signal handler can run.
* Only define RUBY_DLN_CHECK_ABI when supportedPeter Zhu2022-03-01-6/+4
|
* ABI checking is not supported on WindowsPeter Zhu2022-03-01-1/+1
|
* dln.c: suppress unused function 'abi_check_enabled_p' warning for wasiYuta Saito2022-03-01-1/+1
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-16 12:55:32 +0000