| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
- The method was renamed from `get` to `get_value`
- Comparing to `String#unpack` isn't quite equivalent, `unpack1` is closer.
- Use frozen_string_literal to avoid allocating a format string every time.
- Use `N` format which is equivalent to `:U32` (`uint_32_t` big-endian).
- Disable experimental warnings to not mess up the output.
Notes:
Merged: https://github.com/ruby/ruby/pull/6221
|
|
https://github.com/ruby/date/commit/0ae93e26aa
|
|
|
|
|
|
https://github.com/ruby/ruby/commit/e4e054e3ce40 used four footnotes
without blank lines. And the ChangeLog generated from that commit
resulted in ``undefined method `parts' for nil`` error.
For now, let a footnote terminated by the next footnote mark.
Also refined the error message when undefined footnote is used.
https://github.com/ruby/rdoc/commit/a7f290130b
|
|
(https://github.com/ruby/rdoc/pull/910)
https://github.com/ruby/rdoc/commit/4e44c9c6cf
|
|
|
|
Since the change at f310ac1cb2964f635f582862763b2155aacf2c12 to show
the backtraces by default, this test started to show the backtraces.
As the backtraces are not the subject of this test, silence them by
using Gem::SilentUI.
Notes:
Merged: https://github.com/ruby/ruby/pull/6220
Merged-By: nobu <nobu@ruby-lang.org>
|
|
Collected `files` lacked `lib` prefix.
Notes:
Merged: https://github.com/ruby/ruby/pull/6219
Merged-By: nobu <nobu@ruby-lang.org>
|
|
When LOAD_RELATIVE, as `sopath` is truncated to the prefix path, make
the duplicate before it. Also make `rb_libruby_selfpath` frozen and
hidden.
|
|
|
|
|
|
The argument of `rb_syswait` is now `rb_pid_t` which may differ from
`int`. Also it is an undefined behavior to take the result of casted
void function (in `rb_protect`).
|
|
`proc_syswait` will be called with a `VALUE` argument.
|
|
gems are unlocked
This is a regression from a change intended to raise errors when user
puts a gem under an incorrect source in the Gemfile by mistake. To fix
the issue, we revert the change that caused it and implement it in a
different way that restores the resolver independency from real
specifications. Now it deals only with names and versions and does not
try to materialize anything into real specifications before resolving.
https://github.com/rubygems/rubygems/commit/d2bf1b86eb
|
|
https://github.com/rubygems/rubygems/commit/d60acdf80d
|
|
https://github.com/rubygems/rubygems/commit/3a843c1ac7
|
|
https://github.com/rubygems/rubygems/commit/9dbc4757a8
|
|
GCC warns of empty format strings, perhaps because they have no
effects in printf() and there are better ways than sprintf().
However, ruby_debug_log() adds informations other than the format,
this warning is not the case.
|
|
|
|
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
Notes:
Merged: https://github.com/ruby/ruby/pull/6212
|
|
I don't think this is super well known so it's worth mentioning as it
can be a pitfall.
See: https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/fopen-wfopen?view=msvc-170
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
Notes:
Merged: https://github.com/ruby/ruby/pull/6212
|
|
See: https://bugs.ruby-lang.org/issues/18882#note-13
[Bug #18882]
Notes:
Merged: https://github.com/ruby/ruby/pull/6212
|
|
|
|
Notes:
Merged-By: BurdetteLamar <BurdetteLamar@Yahoo.com>
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6214
|
|
As discussed in [Bug #18911], I'm adding some documentation to
`Process._fork` to clarify that it is not expected to cover
calls to `Process.daemon`.
[Bug #18911]: https://bugs.ruby-lang.org/issues/18911
Co-authored-by: Yusuke Endoh <mame@ruby-lang.org>
Notes:
Merged: https://github.com/ruby/ruby/pull/6170
Merged-By: nobu <nobu@ruby-lang.org>
|
|
https://github.com/rubygems/rubygems/commit/3cc3bfd371
|
|
https://github.com/rubygems/rubygems/commit/69d0b4e10b
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6203
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6203
|
|
Gemspec files generated by old bundler run `git` without changing the
working directory.
Or some gemspec files expect an owned file at the top exists ath the
current working directory.
Notes:
Merged: https://github.com/ruby/ruby/pull/6203
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6203
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6203
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6203
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6203
|
|
|
|
opt_aref_with is an optimized instruction for accessing a Hash using a
non-frozen string key (ie. from a file without frozen_string_literal).
It attempts to avoid allocating the string, and instead silently using a
frozen string (hash string keys are always fstrings).
Because this is just an optimization, it should be invisible to the
user. However, previously this optimization was could be seen via hashes
with default procs.
For example, previously:
h = Hash.new { |h, k| k.frozen? }
str = "foo"
h[str] # false
h["foo"] # true when optimizations enabled
This commit checks that the Hash doesn't have a default proc when using
opt_aref_with.
Notes:
Merged: https://github.com/ruby/ruby/pull/6196
|
|
Allow str-concat arg to be any string subtype, not just rb_cString
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
* YJIT: Add known_* helpers for Type
This adds a few helpers to Type which all return Options representing
what is known, from a Ruby perspective, about the type.
This includes:
* known_class_of: If known, the class represented by this type
* known_value_type: If known, the T_ value type
* known_exact_value: If known, the exact VALUE represented by this type
(currently this is only available for true/false/nil)
* known_truthy: If known, whether or not this value evaluates as true
(not false or nil)
The goal of this is to abstract away the specifics of the mappings
between types wherever possible from the codegen. For example previously
by introducing Type::CString as a more specific version of
Type::TString, uses of Type::TString in codegen needed to be updated to
check either case. Now by using known_value_type, at least in theory we
can introduce new types with minimal (if any) codegen changes.
I think rust's Option type allows us to represent this uncertainty
fairly well, and should help avoid mistakes, and the matching using this
turned out pretty cleanly.
* YJIT: Use known_value_type for checktype
* YJIT: Use known_value_type for T_STRING check
* YJIT: Use known_class_of in guard_known_klass
* YJIT: Use known truthyness in jit_rb_obj_not
* YJIT: Rename known_class_of => known_class
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
|
|
```
/Users/deivid/Code/rubygems/rubygems/test/rubygems/test_gem_resolver_installer_set.rb:55: warning: assigned but unused variable - a_1_local
```
https://github.com/rubygems/rubygems/commit/9ea4534800
|
|
When I removed the SizeQueue#push timeout from my PR, I forgot to
update the `queue_sleep` parameters to be a `queue_sleep_arg`.
Somehow this worked on most archs, but on Solaris/Sparc it would
legitimately crash when trying to access the `timeout` and `end`
members of the struct.
Notes:
Merged: https://github.com/ruby/ruby/pull/6213
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6193
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6193
|
|
Adding `ruby` to `PREP` causes the following circular dependencies
because `PREP` is used as a prerequisite by some targets required to
build `ruby` target itself.
```
make: Circular .rbconfig.time <- ruby dependency dropped.
make: Circular builtin_binary.inc <- ruby dependency dropped.
make: Circular ext/extinit.c <- ruby dependency dropped.
make: Circular ruby <- ruby dependency dropped.
```
Adding a new Make variable like `EXTPREP` only for exts may be also
reasonable, but it would introduce another complexity into our build
system. `-bundle_loader` doesn't care that link-time and run-time
loader executables are different as long as bound symbols are provided,
so it's ok to resolve from miniruby to simplify our build.
Notes:
Merged: https://github.com/ruby/ruby/pull/6193
|
|
For the macOS -bundle_loader linker option, we need a path to the
Ruby exectuable. $(RUBY) is not necessarily a path since it could
be a command line invocation. That happens during build with
runruby.rb and can happen post installation if the user passes
the --ruby option to a extconf.rb. Use $(bindir) to locate
the executable instead.
Before installation, $(bindir) doesn't exist, so we need to be
able to override $(BUILTRUBY) in such situations so test-spec
and bundled extensions could build. Use a new mkmf global,
$builtruby, to do this; set it in fake.rb and in extmk.rb.
Our build system is quite complex...
Notes:
Merged: https://github.com/ruby/ruby/pull/6193
|