summaryrefslogtreecommitdiff
path: root/lib
AgeCommit message (Collapse)Author
2024-01-25[ruby/irb] recever ==> receiverydah
https://github.com/ruby/irb/commit/dbd0e368c4
2024-01-25[ruby/irb] inifinity ==> infinityydah
https://github.com/ruby/irb/commit/78dea58000
2024-01-24[rubygems/rubygems] Keep compatibility of past versionsHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/54b67fb251
2024-01-24[rubygems/rubygems] Skip to load commented out wordsHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/e6a9148ba2
2024-01-24Revert "Ensure File.open applies default umask on gem extract"Hiroshi SHIBATA
This reverts commit 01f9766aa05182a7bbdc914a5dcd8a36ebade861.
2024-01-24[rubygems/rubygems] Remove no longer necessary codeDavid Rodríguez
https://github.com/rubygems/rubygems/commit/b7d2de2ba8
2024-01-24[rubygems/rubygems] Fix rake extension warningなつき
https://github.com/rubygems/rubygems/commit/04973e349c
2024-01-24Ensure File.open applies default umask on gem extractMartin Emde
2024-01-22Extract csvHiroshi SHIBATA
2024-01-22Extract nkfHiroshi SHIBATA
2024-01-22[ruby/irb] Fix documentation typo, `niL` -> `nil`Eddie Lebow
https://github.com/ruby/irb/commit/79086a9dda
2024-01-22Extract drbHiroshi SHIBATA
2024-01-22Reapply "[rubygems/rubygems] Fix activation conflicts when circularly ↵Hiroshi SHIBATA
requiring a gem" This reverts commit 04cf66765a8a9d48baea6d9aee266dc9aa21df27.
2024-01-22Reapply "[rubygems/rubygems] Fix `require` of a default gem when unresolved ↵Hiroshi SHIBATA
gems depend on it" This reverts commit 54552b89e73fc616ba47c1c87d33625af99cbce9.
2024-01-22[ruby/uri] Removed commented-out codeHiroshi SHIBATA
https://github.com/ruby/uri/commit/feb8e0dd73
2024-01-22[ruby/nkf] Add JRuby extension to the gemCharles Oliver Nutter
This pulls in the nkf extension implementation from JRuby. The build and load logic has been updated along the same lines as ruby/digest and the gem appears to build correctly for the -java platform. Fixes https://github.com/ruby/nkf/pull/13 https://github.com/ruby/nkf/commit/18f57f36ed
2024-01-19[ruby/prism] switch unless to ifAdam Hess
https://github.com/ruby/prism/commit/29bdbf4212 Co-authored-by: Kevin Newton <[email protected]>
2024-01-19[ruby/prism] Handle stovetop start in constant path fullnameAdam Hess
https://github.com/ruby/prism/commit/3a216e63fe
2024-01-19[ruby/prism] Parsing rules documentKevin Newton
https://github.com/ruby/prism/commit/57a9575543
2024-01-19[ruby/prism] Extract identifier lexing documentation to separate fileMatthew Healy
https://github.com/ruby/prism/commit/c9df17e3c0
2024-01-19Extract rindaHiroshi SHIBATA
2024-01-19Extract resolv-replaceHiroshi SHIBATA
2024-01-19Extract abbrev as bundled gemsHiroshi SHIBATA
2024-01-19Extract observer as bundled gemsHiroshi SHIBATA
2024-01-19Revert "[rubygems/rubygems] Fix `require` of a default gem when unresolved ↵Hiroshi SHIBATA
gems depend on it" This reverts commit f1f5f22d22a149f20e019728b1ab35593d29d81a.
2024-01-19Revert "[rubygems/rubygems] Fix activation conflicts when circularly ↵Hiroshi SHIBATA
requiring a gem" This reverts commit db44088c2a92040879386aa5f268db4c858e4e5b. https://github.com/ruby/ruby/actions/runs/7578672002/job/20641640821 https://github.com/ruby/ruby/actions/runs/7578672002/job/20641641212 https://github.com/ruby/ruby/actions/runs/7578672002/job/20641642031
2024-01-19[rubygems/rubygems] Fix activation conflicts when circularly requiring a gemDavid Rodríguez
If a gem is required circular, and there are unresolved specs depending on it, we may end up in an activation conflict. The solution is to not try to activate unresolved gems when requiring a default gem, regardless of it having already been activated or not. https://github.com/rubygems/rubygems/commit/3b2b8f4e3e
2024-01-19[rubygems/rubygems] Fix `require` of a default gem when unresolved gems ↵David Rodríguez
depend on it The following conditions must be met: * A default gem is required. * A previous require left some gems unresolved, and those dependencies themselves depend on the default gem. In this case, rubygems require will first activate the default version of the gem, then try to activate another unresolved version of the default gem that conflicts with the first activation. The solution is, if we are in the middle of requiring a default gem, skip this step, because we have already activated it successfully. https://github.com/rubygems/rubygems/commit/8cd5608db5 Co-authored-by: Stan Hu <[email protected]>
2024-01-19[rubygems/rubygems] Add a comment to explain default gem activationDavid Rodríguez
https://github.com/rubygems/rubygems/commit/291128268f
2024-01-19[ruby/irb] Bump version to v1.11.1Stan Lo
(https://github.com/ruby/irb/pull/837) https://github.com/ruby/irb/commit/f052097c4b
2024-01-18RJIT: Properly reject keyword splat with `yield`Alan Wu
See the fix for YJIT.
2024-01-18[rubygems/rubygems] Drop two TODOs from specification.rbOlle Jonsson
These were introduced 13 years ago, in a documentation update. Perhaps we can let the TODOs go, without taking any action? https://github.com/rubygems/rubygems/commit/fb23fa84f9
2024-01-16Drop obsoleted BUILTIN_ATTR_NO_GC attributeTakashi Kokubun
The thing that has used this in the past was very buggy, and we've never revisied it. Let's remove it until we need it again.
2024-01-17Extract base64 as bundled gemsHiroshi SHIBATA
2024-01-16[ruby/prism] Add parse options to JavaScript's parsePrism functionCameron Dutro
https://github.com/ruby/prism/commit/d7fe7c7ae7
2024-01-16[ruby/prism] Fix up gemspecKevin Newton
https://github.com/ruby/prism/commit/82e3126762
2024-01-16[ruby/prism] First pass at documenting information about the CRuby compilerJemma Issroff
https://github.com/ruby/prism/commit/b575914b2f
2024-01-16Extract getoptlong as bundled gemsHiroshi SHIBATA
2024-01-15[ruby/pp] Print beginless ranges properlySamuel Giddins
Instead of displaying the start of the range as nil https://github.com/ruby/pp/commit/1df210d903
2024-01-11[ruby/pp] Fix pretty printing a Data subclass instance when the subclass is ↵Benoit Daloze
anonymous * It would be "#<data a=42>" (double space) instead of "#<data a=42>" (like #inspect). https://github.com/ruby/pp/commit/bed72bfcb8
2024-01-11[ruby/pp] Use .class.members for pretty printing DataBenoit Daloze
* Data#members might not be defined, instead it might be defined on Data subclasses or a module included there. This is notably the case on TruffleRuby which defines it there for optimization purposes. In fact the mere presence of Data#members implies a megamorphic call inside, so it seems best to avoid relying on its existence. https://github.com/ruby/pp/commit/6a97d36fbb
2024-01-11[ruby/pp] Use a proper feature check to check if Data is definedBenoit Daloze
https://github.com/ruby/pp/commit/ed602b9f2b
2024-01-11[ruby/rdoc] Respect modeline to detect parserNobuyoshi Nakada
https://github.com/ruby/rdoc/commit/485468f06f
2024-01-11[rubygems/rubygems] Always avoid "Updating rubygems-update" messageDavid Rodríguez
The fact that under the hood the upgrade is done through a rubygems-update gem is an implementation detail that does not really help users to know. Plus, it reads a bit weird. https://github.com/rubygems/rubygems/commit/0fa5c50258
2024-01-11[rubygems/rubygems] Make `gem update --system` respect ruby version constraintsDavid Rodríguez
https://github.com/rubygems/rubygems/commit/36052abbe2
2024-01-11[rubygems/rubygems] Remove old condition no longer necessaryDavid Rodríguez
https://github.com/rubygems/rubygems/commit/701980b240
2024-01-11[rubygems/rubygems] Fix development dependency not being added if introduced ↵David Rodríguez
by two gemspecs https://github.com/rubygems/rubygems/commit/adc05bf1c3
2024-01-11Complete missing specs for platforms after resolutionDavid Rodríguez
If two platform specific variants have different dependencies, then resolution may fallback to the non platform specific variant. However, the platform specific variants that have the same dependencies as the non specific one can still be kept. Do a pass to complete those after resolution.
2024-01-11[rubygems/rubygems] Move resetting the spec set to where it becomes necessaryDavid Rodríguez
https://github.com/rubygems/rubygems/commit/a8b547c6b1
2024-01-11[rubygems/rubygems] Extract a couple of helper methodsDavid Rodríguez
https://github.com/rubygems/rubygems/commit/880a4eae7f
generated by cgit v1.2.3 (git 2.25.1) at 2025-05-28 04:44:22 +0000