Activity
From 05/22/2022 to 05/28/2022
05/28/2022
-
11:06 PM Bug #18765 (Closed): Wrong description introduced by https://github.com/ruby/ruby/pull/4938/files
- 07:20 PM Revision 931b013b (git): * 2022-05-29 [ci skip]
-
07:20 PM Revision 8038d5e4 (git): Revert flawed doc for slice_after, slice_when, and chunk_while (#5952)
- Restores doc for the methods that were cited in https://bugs.ruby-lang.org/issues/18765.
-
10:22 AM Revision 6e3295e5 (git): [rubygems/rubygems] Make code to find target update version easier to follow
- https://github.com/rubygems/rubygems/commit/a7f81cc7ee
-
- It's already done before.
https://github.com/rubygems/rubygems/commit/49d28cfde5 -
- https://github.com/rubygems/rubygems/commit/9f3b21192d
-
06:26 AM Feature #18809: Add Numeric#ceildiv
- Julia provides [`cld`](https://docs.julialang.org/en/v1/base/math/#Base.cld) and [`fld`](https://docs.julialang.org/en/v1/base/math/#Base.fld) for the ceiling and flooring division, respectively. They are implemented as aliases of `div`...
-
01:50 AM Feature #18809: Add Numeric#ceildiv
- I'm positive.
It may be nice to alias `div` as `floordiv` too? -
04:20 AM Misc #18689 (Closed): Windows mswin builds, Actions, OpenSSL 3
-
04:16 AM Misc #18689: Windows mswin builds, Actions, OpenSSL 3
- All of the above has been implemented. Re Actions & Windows builds, using an mswin build (currently only available as a head build, 'mswin') will install all the vcpkg dependencies needed to build Ruby, similar to mingw & ucrt builds. ...
-
04:16 AM Bug #18810: Make `Kernel#p` interruptable.
- PR: https://github.com/ruby/ruby/pull/5967
-
- While figuring out https://bugs.ruby-lang.org/issues/18465 I found a test which fails when `rb_io_flush` becomes blocking.: https://github.com/ruby/ruby/commit/fe6b2e20e9f17ed2c2900aa72994e075ffdc7124
It seems unusual to me that `Kern... -
- Merged changes and follow up issue: https://bugs.ruby-lang.org/issues/18810
-
-
- In some cases, `Kernel#p` can block when calling `rb_io_flush` if the output is a pipe. Because of that, `rb_io_blocking_region` can be interrupted while doing flush. This causes the spec `test_async_interrupt_and_p` to fail, because it ...
- 03:44 AM Revision 6b0131db (git): Make `Kernel#p` completely uninterruptible.
- 03:44 AM Revision 753d3055 (git): Tidy up usage of write_lock.
- 03:44 AM Revision 1589ac62 (git): Improve handling of zero length writes.
- 03:44 AM Revision 4efccd28 (git): Improve consistency of `io_binwritev_internal` implementaiton.
- 03:44 AM Revision ac499bb5 (git): Improve error handling in `finish_writeconv`.
- 03:44 AM Revision c6cd9e18 (git): Better handling of `error`.
- 03:44 AM Revision 585e9714 (git): Always allocate write_lock
- 03:44 AM Revision 216593f5 (git): Add IO write throughput/locking overhead benchmark.
- 03:44 AM Revision 15ebfe28 (git): Make `io_binwritev` atomic.
- 03:44 AM Revision ce23cfa5 (git): Make `io_binwrite` atomic.
-
-
- This is working as expected, we have implemented it in the async gem.
05/27/2022
-
10:23 PM Feature #18809 (Closed): Add Numeric#ceildiv
- pull request: https://github.com/ruby/ruby/pull/5965
I have needed to implement "rounding up division" several times.
("rounding up division" means getting a quotient of division which is rounded up to the nearest integer.)
Typi... -
08:45 PM Revision 8a13a2e8 (git): RCLASS uses FLUSER bits 0 through 3
-
- 08:38 PM Revision c3fd2e49 (git): * 2022-05-28 [ci skip]
-
08:38 PM Revision fc184ca1 (git): Only check class ancestors for ivar in memory_view
- rb_class_get_superclass returns the immediate SUPER, including T_ICLASS.
rb_ivar_lookup isn't implemented for T_ICLASS so it uses the default
behaviour, which always returns Qnil.
This commit avoids checking T_ICLASS for ivars. -
-
10:17 AM Bug #18806: protected methods defined by refinements can't be called
- Right, agreed that 1 is best semantically.
I'm not too keen on extra checks, but the checks for protected are already expensive and this won't make it significantly worse.
1 implies 2 BTW in terms of optimizations, i.e., if it's an f... -
07:07 AM Bug #18806: protected methods defined by refinements can't be called
- protected is for a method call with an explicit receiver, so I prefer 1.
private is enough for fcalls.
-
- Instead of guessing on the culprit.
We actually have a helper, `Bundler.rm_rf`, with exactly the behavior
that we want:
* Allow the passed folder to not exist.
* No exception swallowing other than that.
https://github.com/rubygems/rub... -
- Follow up of https://github.com/ruby/ruby/pull/5927
`pthread_threadid_np()` is not even be declared in outdated SDKs.
Also, the `__API_AVAILABLE` macro does not work on gcc, which does not
support the [availability] attribute of clang,... -
04:10 AM Bug #18608: `require': cannot load such file -- ripper (LoadError) after `make distclean`
- I guess this is because either `bison` is not installed in the build environment or the environment variable `YACC` is not correctly set. Note that `make distclean` among other things removes `ext/ripper/ripper.c` which requires `YACC` (...
-
-
- This reverts commit 2f5edfa47d06c9605a5a0aa3ad72d7fef4d44fa3.
05/26/2022
-
-
- I've submitted a pull request to fix this: https://github.com/ruby/stringio/pull/30
-
-
- I tested this on several Linux (GNU/Linux and Android) environments. Sending `Ctrl-Z` from terminal sometimes results in "Received ..." and sometimes "deadlock" but not sticking to one result for each environment. I used the newest relea...
-
- I agree that the behavior for all of these methods should be the same. I think the IO behavior makes the most sense, and String and StringIO should be changed to match it.
I submitted pull requests to Ruby (https://github.com/ruby/ru... -
09:45 PM Bug #18286: Universal arm64/x86_84 binary built on an x86_64 machine segfaults/is killed on arm64
- I don't believe any of those bugs are related.
My suspicion is that, when building on x86 and targeting universal, during `configure` for cross-compilation on arm64 the small test binaries that built cannot be executed on x86, leading... -
- I think both IO#each and StringIO#each behavior is wrong when combining `nil` with `chomp`. My opinion is that a `nil` separator means there is no separator at all, and therefore `chomp` should either raise an error or be ignored if `ni...
-
- I agree this looks like unintended behavior/a bug.
TruffleRuby already behaves like:
```
:refined
:refined
:refined
:refined
"method"
```
fcalls should ignore visibility, always, so I think 2. is best. -
- Hello!
The `protected` visibility is a bit unusual, since it depends on where the callee method is considered to be defined. I was looking into making [an optimization](https://github.com/ruby/ruby/pull/5643) to calling `protected` me... -
- I've submitted a pull request to fix this: https://github.com/ruby/ruby/pull/5954
-
- I've submitted a pull request to fix this: https://github.com/ruby/ruby/pull/5953
-
-
-
-
06:03 PM Bug #18807: /lib/x86_64-linux-gnu/libruby-2.7.so.2.7 issue
- Kakcalu13 (Kevin KO) wrote in #note-2:
> xtkoba (Tee KOBAYASHI) wrote in #note-1:
> ...
Wait, how do you close this issue? lol -
- xtkoba (Tee KOBAYASHI) wrote in #note-1:
> Note that the stack trace shows most recent call last. I guess Ruby Core is not much relevant here because it only calls `runGui` in `libignition-gazebo3-ign.so.3.12.0` through FFI. If anything... -
- Note that the stack trace shows most recent call last. I guess Ruby Core is not much relevant here because it only calls `runGui` in `libignition-gazebo3-ign.so.3.12.0` through FFI. If anything, then the parameters for `runGui` might hav...
-
- Seems like this is the right place for this issue. If this is wrong place, please let me know so I can close it promptly
My computer specs:
OS: MacOS Monetery
CPU/GPU: Apple chip (M1)
Docker: Ubuntu 20.04 Focal
I was able to... -
- Is `^C` after `irb(main):005:0> a1` intentional?
In my experiment, interruption (`Ctrl-C`) in the middle of evaluation seems to cause `irb` to exit, but I don't know if it is relevant here.
```
$ irb
irb(main):001:0> a1^C
irb(ma... - 05:07 PM Revision c3929b8c (git): * 2022-05-27 [ci skip]
- 05:06 PM Revision ba887870 (git): Use bindgen to import CRuby constants for YARV instruction bytecodes
-
02:52 PM Bug #18808 (Closed): Cannot compile ruby 3.1.2 on powerpc64le-linux without disabling the jit features
- The system I am trying to compile on is a ppc64el system running RedHat 7 (3.10.0-1160.62.1.el7.ppc64le). I can successfully compile on a x86_64 system running the same version RedHat 7 (3.10.0-1160.62.1.el7.x86_64)
When I configure ... - 01:04 PM Revision bd472ef3 (git): Show ASAN_OPTIONS in hacking guide.
-
10:55 AM Revision 46cf3bf3 (git): Using TZMODE_SET_LOCALTIME macro
-
- 04:51 AM Revision 2556e15d (git): Remove unnecessary ignore warnings.
-
- https://github.com/ruby/ruby/pull/5946 experiment with `clang-format`.
- 02:20 AM Revision 946e3bbd (git): Simplify the autoload require logic.
05/25/2022
- 10:08 PM Revision 982bf726 (git): * 2022-05-26 [ci skip]
-
- https://github.com/ruby/fileutils/commit/27a3c376c7
-
- This seems the same as #18779, which just got fixed.
-
-
- I agree that this isn't a bug.
In terms of `openssl/cipher`, requiring individual parts of a library should never be assumed to be supported unless the library is explicitly designed for that. We shouldn't attempt to detect invalid r... -
- dorianmariefr (Dorian Marié) wrote in #note-2:
> Should the fix be backported?
If you can bisect and find the fixing commit, we can mark it for backporting. Whether to backport is always up to the branch maintainer. -
06:07 PM Bug #18801: Dead YARV instructions produced when `branchif` is used
- Both of those instructions serve a purpose, but they could also be optimized away.
`next_catch_label` is referenced from the catch table. That catch table may be optimized away, which is why you are seeing the label being omitted from... -
12:20 PM Bug #18801: Dead YARV instructions produced when `branchif` is used
- My questions aside. I'm not sure this is a bug, and could probably be closed?
-
I investigated these instructions and whether or not they were dead code and
could be removed.
From the outside it looks like there are two things to note:
* they immediately follow an unconditional jump and so should theoretica...-
01:57 PM Misc #18800: The administrator requires you to enable two-factor authentication.
- Oh I see. I thought 2FA was for protecting our accounts, but instead it's to increase barrier to entry for bots (but also for humans). Not sure I agree, but I understand your pain.
-
12:59 PM Bug #18793: Select and Find behave differently for hashes
- Yeah, I had noticed the difference, but I assumed that "method missing = bug". But you are right. That would be a breaking change for a lot of projects (I hand't thought of that).
-
12:58 PM Bug #18658: Need openssl 3 support for Ubuntu 22.04 (Ruby 2.7.x and 3.0.x)
- Having helped several co-workers to install ruby-2.7 and 3.0 on their Ubuntu-22.04, I support backporting the openssl-3.0 gem to these ruby versions, similar to how Ubuntu patched their ruby-3.0 package. While it's preferable to use the ...
-
12:45 PM Bug #18805 (Closed): IO::Buffer is inconsistent when returning a string from an empty buffer
- I’ve been using `IO::Buffer` and I found it to be slightly inconsistent when it comes to returning empty string for empty buffers.
for example, a slice of an allocated buffer with `size = 0`, returns `""` with `get_string`, as an exampl... - 12:17 PM Revision d875445e (git): Fix GC race condition in autoload.
-
12:02 PM Feature #14602: Version of dig that raises error if a key is not present
- What about simply allowing `fetch` to take multiple arguments?
If there are more than one argument, always interpret the last one as the default value unless when there is a block, in which case, the block is evaluated if a key is missi... -
06:45 AM Feature #14602: Version of dig that raises error if a key is not present
- I fully agree with @duerst in #14602#note-24:
> maybe we can think it as a combination of `dig` with `fetch`. Then what about `dig_fetch` or `fetch_dig`? These names don't look very natural, but it's easy to understand what they are ... -
12:04 AM Feature #14602: Version of dig that raises error if a key is not present
- My humble suggestion would be `Hash#retrieve`. The operation tries to retrieve a value in the depths of a hash and if it comes back empty handed, that is an error.
```ruby
hash = {
name: {
first: "Ariel",
last: "Caplan"
... -
- https://github.com/ruby/timeout/commit/f3a31abdfb
-
-
- https://github.com/ruby/timeout/commit/5153ae9cad
-
- https://github.com/ruby/timeout/commit/01c44b591f
- 09:50 AM Revision 952ff7fb (git): Fix out of bounds read.
- 09:50 AM Revision 86602484 (git): Ensure we retain the main fiber stack bounds.
-
-
- https://github.com/ruby/timeout/commit/9a9b03b44c
-
-
09:22 AM Bug #18804 (Open): Invalid line number for putnil instruction
- Looks like this is a pretty old bug. Consider example:
```
def foo1
if true
nil
else
1
end
end
def foo2
if true
42
else
1
end
end
foo1_method = method(:foo1)
puts RubyVM::InstructionSequen... - 09:09 AM Revision ab7f8e32 (git): Update default gems list at fde4519af8762fccc8488d1972d984 [ci skip]
-
- https://github.com/ruby/timeout/commit/f69f954a94
-
- As eregon stated, it's an intended limitation.
It's possible to allow importing C methods without refinements activation.
It may be helpful for attr_*, but not for define_method.
-
-
03:59 AM Misc #18803 (Closed): DevMeeting-2022-06-16
- # The next dev meeting
**Date: 2022/06/16 13:00-17:00** (JST)
Log: https://github.com/ruby/dev-meeting-log/blob/master/DevMeeting-2022-06-16.md
- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bu... -
-
03:34 AM Bug #18802: Negation of POSIX character class does not work
- Thank you! I misunderstood about character classes.
-
- Note that the sentence is written in [the section of character class](https://docs.ruby-lang.org/ja/3.1/doc/spec=2fregexp.html#string). So `[:^ascii:]` must be used in a character class as follows:
```
irb(main):001:0> %w[あああ あ a b :... -
- > https://docs.ruby-lang.org/ja/3.1/doc/spec=2fregexp.html#charclass_posix
> ...
For example, `[:^ascii:]` is the negation of `[:ascii:]` according to the document. But it does not work:
```ruby
irb(main):001:0> RUBY_VERSION
=> "3.... - 03:24 AM Revision 9a8fc4e0 (git): Tidy up redundant returns.
- 03:24 AM Revision 42bcc629 (git): Retain reference to blocking fibers.
- 03:24 AM Revision 901525b1 (git): Add support for address sanitizer for amd64 and arm64.
-
12:32 AM Feature #18798: `UnboundMethod#==` with inherited classes
- ah, mistake...
-
- Ah, yes, it is a feature request.
05/24/2022
-
11:34 PM Feature #14602: Version of dig that raises error if a key is not present
- amcaplan (Ariel Caplan) wrote in #note-23:
> We can think of this as either a variation of `fetch` or a variation of `dig`. Ultimately it's both, of course, just depends how you look at it.
Or maybe we can think it as a combination o... -
10:02 PM Feature #14602: Version of dig that raises error if a key is not present
- We can think of this as either a variation of `fetch` or a variation of `dig`. Ultimately it's both, of course, just depends how you look at it.
If we think of it as `fetch`-based, `deep_fetch` would be OK but we also might go with so... -
09:56 PM Feature #14602: Version of dig that raises error if a key is not present
- Considering `dig` as an operation that can be done manually (with fingers) and address exceptional situations (unexpected objects) more subtly, I would suggest `shovel` which is a more blunt instrument which tends to raise a notable exce...
-
08:19 PM Feature #14602: Version of dig that raises error if a key is not present
- Maybe:
``` ruby
fetch_each(:name, :first)
fetch_all(:name, :first)
fetch_tail(:name, :first)
fetch_end(:name, :first)
# or with dig_
dig_each(:name, :first)
dig_tail(:name, :first)
dig_all(:name, :first)
dig_end(:name, :first)
dig_bot... -
07:16 PM Feature #14602: Version of dig that raises error if a key is not present
- Some ideas:
reveal
uncover
unfold
dive
enlight
scoop
reel -
06:16 PM Feature #14602: Version of dig that raises error if a key is not present
- How about `dig_for`? If we’re digging for something, it kinda makes sense to raise an exception if it’s not there.
-
05:50 PM Feature #14602: Version of dig that raises error if a key is not present
- A couple other ideas I had:
- `lookup`
- `pick`
- `traverse` -
- Unfortunately, I have no plan to disable it.
We are always attacked by spammers and crackers. I have no idea to prevent our place from them. -
- Can we please disable mandatory two-factor authentication in this tracker? Offering 2fa is great, but being mandatory is not. For my part I find it completely overblown and superfluous for a site such as this. (And if it's mandatory why ...
-
10:45 PM Bug #18791: Unexpected behavior of Socket#connect_nonblock
- The document does mention the returned value of `0`, but I'm not sure if I should also check for `EISCONN` by calling it one more time in such a case.
-
- @jeremyevans0
The example is overly simplified, and it does lead to confusion in practice when you put it in context.
Realistically speaking, no one would use a single value in `IO.select`; at least, in the worst-case scenario.
So... -
- This doesn't look like a bug. If the `connect` system call returns `0`, then you were able to connect, and `connect_nonblock` in Ruby returns `0` as well. Yes, you should treat `0` as indicating the connection was successful. The docu...
-
09:34 PM Revision d020334e (git): [ruby/reline] Workaround libncurses.so as a linker script
- This maybe isn't probably isn't the best approach, but it will allow
`Fiddle::Terminfo.curses_dl` to work. I documented more details about
this in an issue on fiddle: https://github.com/ruby/fiddle/issues/107
It is probably better to d... -
- > is not defined with Ruby code
It means the method's body is not Ruby code. And indeed, `attr_*` defines methods which are not defined in/with Ruby code.
So this seems expected.
Same for define_method, which has some internal w... -
01:59 AM Bug #18799: Refinement#import_methods vs attr_reader
- UPD: looks like `define_method` is not supported, too:
```ruby
module M
define_method(:fuu) { }
end
module R
refine Object do
import_methods M
end
end
#=> Can't import method which is not defined with Ruby code:... -
- Currently, it's not possible to import methods defined as attr_{reader, accessor,writer}:
```ruby
module M
attr_reader :fuu
end
module R
refine Object do
import_methods M
end
end
#=> Can't import method which is... -
- Regarding Method#==, I think it should also respects the simple rule "point to a same method definition" + ensure the receiver is the same object for both Method instances.
-
- +1. @ko1 I guess you meant this as a feature request?
-
- I'm not against this change (for UnboundMethod, I think Method should remain different), but it seems more like a feature request than a bug fix to me.
-
- Did you mean:
```ruby
p $mc.owner == $md.owner #=> true
p $mc.source_location == $md.source_location #=> true
```
I think the proposal is a good idea. -
- Now `UnboundMethod` for a same method from a superclass and an inherited class are not `==`.
```ruby
class C
def foo = :C
$mc = instance_method(:foo)
end
class D < C
$md = instance_method(:foo)
end
p $mc == $md #=> f... -
- I don't think this is a bug. The behavior difference is because `Hash#each` yields an array of `[key, value]` and not `key` and `value` separately, unlike `Hash#select`.
You can get the behavior you want by using explicit block varia... -
- wildmaples (Maple Ong) wrote:
> It seems there are unused YARV instructions produced when the snippet contains a `branchif` instruction.
> ...
I'm not sure this is `branchif` related. It looks like `while true; end` generates the same ... -
05:39 PM Bug #18801 (Rejected): Dead YARV instructions produced when `branchif` is used
- # Description
It seems there are unused YARV instructions produced when the snippet contains a `branchif` instruction.
In the following example, the instructions numbers 0002 to 0004 won't ever be executed:
```
irb(main):003:0... -
- Fixed via [Bug #18779]
-
- The PR was merged so we can now close this.
I'm marking 3.0 and 3.1 for backport. The two commits are:
- `0de1495f358e9b892dfa63d4b74f59b1d2903703`
- `0c36ba53192c5a0d245c9b626e4346a32d7d144e`
-
04:40 PM Revision 0c36ba53 (git): Define unsupported GC compaction methods as rb_f_notimplement
- Fixes [Bug #18779]
Define the following methods as `rb_f_notimplement` on unsupported
platforms:
- GC.compact
- GC.auto_compact
- GC.auto_compact=
- GC.latest_compact_info
- GC.verify_compaction_references
This change allows users to ... -
- These methods are removed from gc.rb and added to gc.c:
- GC.compact
- GC.auto_compact
- GC.auto_compact=
- GC.latest_compact_info
- GC.verify_compaction_references
This is a prefactor to allow setting these methods to
`rb_f_notimpleme... -
- https://github.com/rubygems/rubygems/commit/84b163e804
-
03:53 PM Bug #18781: MJIT tests failing with Ubuntu focal with gcc-11 and some flags
- I sent the PR, https://github.com/ruby/ruby/pull/5938 .
-
- On the latest master `633608ebd4cbdeea562dc4c608495134965a19a9`, I am testing.
```
$ ./configure --enable-shared --enable-mkmf-verbose --with-gcc="gcc -O2 -fcf-protection" ldflags=-Wl,-z,now
$ make V=1 2>&1 | tee make.log
```
Th... -
- > Could you take a look at fixing your configuration of GitHub Actions?
@k0kubun Thanks for the investigation! Sure. I will fix the GitHub Actions configuration file to use your suggested case `--with-gcc="gcc -O2 -fcf-protection" ldf... - 03:38 PM Revision c603f897 (git): * 2022-05-25 [ci skip]
-
- https://github.com/ruby/fileutils/commit/a4da433443
-
- https://github.com/rubygems/rubygems/commit/b69e1e9374
-
- Move th->altstack to th->nt->altstack.
-
- https://github.com/ruby/date/commit/6d7ab08ffc
-
- This macro is no longer used ([GH-5933]).
-
-
- (but it was already commented out)
-
- `thread_debug()` was introduced to print debug messages
on `THREAD_DEBUG > 0` but `RUBY_DEBUG_LOG()` is more controllable. -
- `rb_th_serial(th)` returns th's serial for debug print purpose.
-
- `NON_SCALAR_THREAD_ID` shows `pthread_t` is non-scalar (non-pointer)
and only s390x is known platform. However, the supporting code is
very complex and it is only used for deubg print information.
So this patch removes the support of `N... -
- caller should check the result of `native_tls_get()`.
05/23/2022
-
- https://github.com/ruby/fileutils/commit/956b345ceb
-
- I've submitted a pull request that addresses this behavior in the way @byroot described above:
https://github.com/ruby/ruby/pull/5934
-
-
- 04:17 PM Revision d270d984 (git): * 2022-05-24 [ci skip]
-
- https://github.com/ruby/fileutils/commit/ff49055f8a
-
-
- https://github.com/ruby/fileutils/commit/db612c5e22
-
- I am asking did_you_mean to use Exception#detailed_message to add
"Did you mean?" suggestion instead of overriding #message method.
https://github.com/ruby/did_you_mean/pull/177
Unfortunately, the change will affect Gem::UnknownCommand... -
11:01 AM Misc #18761: provide an example wasm project
- grosser (Michael Grosser) wrote:
> Neither the release notes nor the wasm/README.md include any runnable examples.
> ...
I assume the final release will have an official .wasm file that ships with it.
Note that the current approach ... -
10:17 AM Feature #18788: Support passing Regexp options as String to Regexp.new
- @nobu
Thank you for the explanation regarding symbols!
> we'll need migration period to warn anything other than inter and valid string
I think the optional third argument should be also deprecated as described in #18797. Otherw... -
- ## Situation
'n' or 'N' can be passed as a third argument to `Regexp.new`. However, the behavior is not the same as the literal `n`-flag or the `Regexp::NOENCODING` option, and it makes the `#encoding` of `Regexp` and `Regexp#source` ... -
09:50 AM Bug #18786: Rescuing NotImplementedError from `GC.verify_compaction_references` can lead to infinite loop on platforms
- I was able to investigate a bit more.
This problem is Ruby 3.1 specific.
I tested the following rubies built from git: 3.0, 3.2preview1, and master branch. Neither of which went into the infinite loop.
I found that if the `gc_veri... -
09:39 AM Feature #14602: Version of dig that raises error if a key is not present
- It seems to be a nice idea. But is `deep_fetch` is the best name for it?
Matz.
-
- RDoc overrides class name by the assigned name unexpectedly when
assigned using a qualified class path.
https://github.com/ruby/net-http/commit/a7bded0407 -
- 03:13 AM Revision 907b1b61 (git): * 2022-05-23 [ci skip]
-
- `pthread_threadid_np` is available since Mac OS X 10.6, use
`pthread_mach_thread_np` on older systems. -
01:49 AM Bug #18795: Verbose GC debug output with -DRGENGC_DEBUG=5 causes a crash
- I had another think about this - the newobj tracepoint is _also_ called in similar circumstances, where the ivar table for a new T_CLASS won't be initialized yet (if using variable length RVALUEs). Thus, calling rb_obj_memsize_of() on an...
-
- This error occurs when lex.c is broken (typically empty).
-
- The GC compaction mechanism uses a kind of read barrier to detect attempts to read objects from pages that have already been moved from (or, at least, I _think_ that's what it does). This is implemented by marking the OS pages as unreada...
05/22/2022
-
- ```ruby
Regexp.new("(?#{options}:#{code})")
```
```ruby
Regexp.new(code, eval("//#{options}").options)
``` -
- I agree that symbols should be disallowed.
The examples uses arbitrary combinations of flags and the order of the flags doesn't have meanings.
In other words, it is a set of chars and OK for a string.
But a symbol is not such thing.
For... -
- Thread-local storage is supported since Mac OS X 10.7. Enable TLS
only when the target version is enough. -
- I was trying to debug an (unrelated) issue in the GC, and wanted to turn on the trace-level GC output by compiling it with -DRGENGC_DEBUG=5. Unfortunately, this actually causes a crash in newobj_init() because the code there tries to lo...
-
- We need thread-local storage on Clang, since 319afed20fba.
-
- 03:02 AM Revision 539459ab (git): Ruby31: add support for Darwin ppc/ppc64 (#5927)
- * add coroutines for ppc & ppc64
* fix universal coroutine to include ppc & ppc64
* add powerpc*-darwin to configure.ac
* fix thread_pthread for older systems