Activity
From 01/06/2022 to 01/12/2022
01/12/2022
-
11:08 PM Revision faf79d3a (git): Enhanced RDoc for IO.popen (#5430)
- * Enhanced RDoc for IO.popen
-
08:56 PM Bug #18482 (Rejected): Fiber can not disable scheduler
- Did you read the documentation?
https://rubyapi.org/3.1/o/fiber#method-c-new -
05:48 PM Bug #18482 (Rejected): Fiber can not disable scheduler
- class Fiber can not disable scheduler with it's parameter.
When parameter is false:
```
require 'fiber'
require 'io/nonblock'
class SimpleScheduler
def initialize
@readable = {}
@writable = {}
@waiting = {}
... -
08:55 PM Revision 2f71f6bb (git): Speed up and avoid kwarg hash alloc in Time.now
- Previously Time.now was switched to use Time.new as it added support for
the in: argument. Unfortunately because Class#new is a cfunc this
requires always allocating a Hash.
This commit switches Time.now back to using a builtin time_s_n... -
08:30 PM Feature #18481: Porting YJIT to Rust (request for feedback)
- maximecb (Maxime Chevalier-Boisvert) wrote in #note-10:
> Would you be provide some specifics of how difficult it would be to compile rust code while packaging Ruby for Fedora/CS/RHEL? Is there an existing rustc package? Would you be ab... -
08:15 PM Feature #18481: Porting YJIT to Rust (request for feedback)
- > TBH, with my Fedora/CS/RHEL maintainer hat on, this proposal scares me.
I completely understand. This is a departure from the Ruby tradition so to speak and as such, has to be considered carefully.
> ...
If it makes you feel any ... -
- maximecb (Maxime Chevalier-Boisvert) wrote in #note-6:
> I'd like to get input from people who are packaging Ruby, and those maintaining Ruby installation scripts.
> ...
Downloading anything (especially binary blobs) or even bundling i... -
07:12 PM Feature #18481: Porting YJIT to Rust (request for feedback)
- maximecb (Maxime Chevalier-Boisvert) wrote in #note-6:
> I'd like to get input from people who are packaging Ruby, and those maintaining Ruby installation scripts.
The current active maintainers of e.g. `ruby-build` would be @hsbt an... -
07:00 PM Feature #18481: Porting YJIT to Rust (request for feedback)
- maximecb (Maxime Chevalier-Boisvert) wrote in #note-6:
> > believe that this is trivially supportable with the use of Rust editions, and if they are able to target the 2018 edition, it would ensure maximum compatibility. A schedule coul... -
- I'd like to get input from people who are packaging Ruby, and those maintaining Ruby installation scripts.
I don't think CRuby should download anything during build. IMO `rustc` should be treated like `gcc`, it's something you should ... -
06:30 PM Feature #18481: Porting YJIT to Rust (request for feedback)
- jeremyevans0 (Jeremy Evans) wrote in #note-2:
> Rust is supposed to be fairly backwards compatible for the last few years. As long as the YJIT team commits to supporting a Rust version that was released more than 12 months ago (say Rus... -
- Eregon (Benoit Daloze) wrote in #note-3:
> jeremyevans0 (Jeremy Evans) wrote in #note-2:
> ...
I don't think that is true, at least not for releases. ruby-3.1.0.tar.gz includes all bundled gems in a `.bundle` directory. `tool/config.... -
- jeremyevans0 (Jeremy Evans) wrote in #note-2:
> I don't think so. Trying to download during a build will result in problems for many packagers.
Yes, for packagers I think they would typically prefer to use an existing Rust package (... -
- Eregon (Benoit Daloze) wrote in #note-1:
> Would it make sense to automatically download a Rust toolchain when building with YJIT?
I don't think so. Trying to download during a build will result in problems for many packagers. Ruby ... -
- Would it make sense to automatically download a Rust toolchain when building with YJIT?
I assume the Rust code would need a specific version of Rust (newer versions might work but not always, backward compat is not eternal) and so it'... -
- TL;DR: The YJIT team wants to explore using Rust to help develop YJIT. The rest of CRuby will continue to build without Rust tools and building YJIT will remain optional.
We’re currently exploring the possibility of porting YJIT to Ru... -
06:22 PM Bug #18475 (Closed): Yielding an element for Enumerator in another thread dumps core
- Applied in changeset commit:git|ae5458f228a5477383e9c00425d85d50a3867817.
----------
thread.c: Convert TAG_BREAK to a normal exception at thread top-level
[Bug #18475] -
- https://github.com/ruby/ruby/pull/5431
-
- This is almost the same issue as #11254. When TAG_BREAK is thrown to the top-level frame, it dumps core. #11254 fixed the case where TAG_BREAK is thrown to the top-level of the main thread, but not of a non-main thread.
I think this p... -
- [Bug #18475]
-
- This is a third-party's issue. See https://github.com/ffi/ffi/issues/864 . You may want to try https://github.com/ffi/ffi/issues/864#issuecomment-875242776 . Or `bundle config --local build.ffi --enable-libffi-alloc`.
-
02:33 PM Bug #18479: I encountered a bug in the Ruby interpreter or extension libraries
- Can you try using Ruby 2.7.5 or newer? Ruby 2.6 is on security maintenance and will be EOL on March 2022.
-
11:39 AM Bug #18479 (Third Party's Issue): I encountered a bug in the Ruby interpreter or extension libraries
- I received a message saying that I encountered a bug in the Ruby interpreter or extension libraries after running the following:
Clone this repo
```
git clone https://github.com/raviriley/agency-jekyll-theme.git
cd agency-jekyll-t... - 05:01 PM Revision 59eb02cd (git): * 2022-01-13 [ci skip]
-
-
- A short (2 bytes) will cause unaligned struct accesses when strings are
used as a buffer to directly store binary data. -
02:53 PM Bug #18468 (Closed): Tutorial Link for Optionparser is broken
- Applied in changeset commit:git|92630e2346a221fdfeaa484632938a06765bc6e5.
----------
[ruby/optparse] Fix links to the page directory files [Bug #18468]
https://github.com/ruby/optparse/commit/dab72c543d -
01:13 PM Bug #18480 (Closed): Dtrace enabled build fails on systems with DTRACE_REBUILD=yes
- When building Ruby 3.1 on Solaris, where dtrace requires a recompilation (DTRACE_REBUILD=yes), the compilation fails with the following linking error:
```
linking miniruby
Undefined first referenced
symbol in file
__dtr... -
- https://github.com/ruby/optparse/commit/9e29d86c12
-
- https://github.com/ruby/optparse/commit/0ac9957696
-
- https://github.com/ruby/optparse/commit/dab72c543d
-
- Specify the main page and the page directory. Also in Rakefile,
extract and use the same options from the gemspec file.
https://github.com/ruby/optparse/commit/d182cd60b5 -
- https://github.com/ruby/optparse/commit/ed283559d4
-
09:57 AM Bug #18472: rb_w32_map_errno is not found on Ruby-3.1.0
- It is because of a change in rubyinstaller-3.1.0-x64.
In https://rubyinstaller.org/2021/12/31/rubyinstaller-3.1.0-1-released.html:
> RubyInstaller-3.1.0-x64 has a changed C-runtime called UCRT replacing the old MSVCRT.
I guess tha... -
-
- I think I understand the issue. When the following code is executed on Ruby 3.0, it prints `"should_not_reach_here"`.
```
def foo
Thread.new do
1.times do
yield
end
p "should_not_reach_here"
end.join
end
... -
02:02 AM Revision dcb02cb2 (git): [ruby/io-nonblock] Use omit instead of skip for test-unit
- https://github.com/ruby/io-nonblock/commit/a7bfbfa049
-
- https://github.com/ruby/rinda/commit/1d3512aa26
-
- https://github.com/ruby/io-wait/commit/75543ab1bc
-
- https://github.com/ruby/date/commit/537f3f681e
-
- https://github.com/ruby/open3/commit/f6ca124b56
-
- https://github.com/ruby/win32ole/commit/2d5dc47ed4
-
- https://github.com/ruby/win32ole/commit/c0586b2f75
-
- https://github.com/ruby/resolv/commit/55e42221d4
-
01:49 AM Revision d494a16a (git): [ruby/resolv] Support more characters in link local addresses
- Implements [Feature #17524]
https://github.com/ruby/resolv/commit/993a1a374f -
01/11/2022
-
07:55 PM Feature #18478 (Open): Module#constant_pairs
- Let's say I have a module like this:
```ruby
module A
B = 1
class C
end
end
```
I can find out its constants with `constants`:
```ruby
A.constants # => [:B, :C]
```
But if I also want to get the values of the cons... -
07:28 PM Feature #18477: Float#sqrt and Integer#sqrt
- See https://twitter.com/kddnewton/status/1480977779688710145 for why I filed this bug
-
- Actually maybe not worth it, also there are a lot of methods from the Math module that could be done like that
-
- Would be nice to do:
```ruby
10.sqrt # => 3.1622776601683795
3.5.sqrt # => 1.8708286933869707
``` - 07:18 PM Revision 421bb589 (git): * 2022-01-12 [ci skip]
- 07:17 PM Revision 14967347 (git): YJIT stats documentation additions and updates (#5427)
- * YJIT documentation additions and updates
* Update yjit.md
Co-authored-by: Maxime Chevalier-Boisvert <maximechevalierb@gmail.com> -
06:30 PM Bug #18476 (Open): Call to require stuck forever after receiving EAGAIN on writev when running with zeus
- # Environment
I'm using Ubuntu 18.04 running on Windows using WSL2:
```
$ uname -a
Linux myhostname 5.10.60.1-microsoft-standard-WSL2 #1 SMP Wed Aug 25 23:20:18 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modu... -
- Thank you for your report.
I don't yet know exactly what's going on, but as far as I see your repro code, the behavior of `yield "some-value"` is different from `1.times { yield "some-value" }` on Ruby 3.0, and they are the same on Ru... -
04:06 PM Bug #18474 (Closed): 938e027c seems to have caused a regression in yield handling with concurrent-ruby
- I'm sorry for the awful title, I don't know enough about what is going on to describe it better. From a debugging perspective it seems that a very specific set of circumstances causes a `begin` block to be jumped out of when a proc it is...
-
- Dan0042 (Daniel DeLorme) wrote in #note-19:
> I was thinking what should be the return value of `each_caller{ }` with no `break`. Building and returning an array of frames seems wasteful since in most cases it would never be used (due t... -
04:47 PM Feature #16663: Add block or filtered forms of Kernel#caller to allow early bail-out
- Sorry, last bikeshed:
I was thinking what should be the return value of `each_caller{ }` with no `break`. Building and returning an array of frames seems wasteful since in most cases it would never be used (due to break), so nil seems a... -
- I faced [BUG] when investigating #18474
```
def run
Thread.new do
1.times do |value|
yield "some-value"
end
end.join
end
to_enum(:run).first
```
```
$ ruby repro.rb
#<Thread:0x00007fcab26af0c0 repro.... -
- If the scheduler hook is called under the write lock that sounds like it could cause additional problems including deadlocks, long waits, etc.
So my POV is the fix as originally proposed with the write lock is incomplete and likely to c... -
05:24 PM Bug #18465: Make `IO#write` atomic.
- "ioquatix (Samuel Williams)" <noreply@ruby-lang.org> wrote:
> By the way, even calling `write` directly is no guarantee of
> synchronous output between threads/processes - on Linux there
> is an informal guarantee of page-sized atomi... -
- @nobu did you mean that the name "description" is vague or the concept itself? Would you find it less vague if it was named something else? (e.g. "detailed_message" or something)
-
- @nobu How so? Do you have an example?
The responsibilities for `description` are to call `super` and include it in the return value. That's it, nothing else.
The same goes for `additional_message` and is necessary if there are mult... -
- `Exception#description` seems to add too much flexibility and make responsibilities vague.
-
- matz (Yukihiro Matsumoto) wrote in #note-19:
> I like the idea of helpers in https://bugs.ruby-lang.org/issues/16122#note-18.
> ...
Having helpers would definitely provide a nice easy experience. But since the important thing here is t... -
07:52 AM Feature #16122: Data: simple immutable value object
- @ko1
> It seems not related to "immutability".
Yes, I covered this, too (I know it is a large wall of text, sorry!), in **Concrete proposal** section:
> Class API is copying Structs one (most of the time -- even reuses the imple... -
07:47 AM Feature #16122: Data: simple immutable value object
- zverok (Victor Shepelev) wrote in #note-24:
> @ko1, the initial ticket provides some explanations:
Sorry I found it just after commented.
It seems not related to "immutability". -
- @ko1, the initial ticket provides some explanations:
> For example, this code snippet shows why `to_a` is problematic:
```ruby
Result = Struct.new(:success, :content)
# Now, imagine that other code assumes `data` could be eithe... -
- I don't use `Enumerable` features of `Struct` classes, but I don't have any trouble by having `Enumerable`.
Why do you want to remove `Enumerable` features?
I can not find any benefits. -
02:13 PM Bug #18473 (Open): Raw data in Socket::Option#inspect on Amazon Linux 2
- Hello,
I found a weird issue when running attached script. Locally on Ubuntu running kernel 5.11, on CI (GitHub Actions) and through docker image (ruby:3.1.0-alpine3.15), the response is as it should be with all data parsed correctly:... -
02:11 PM Bug #18472 (Closed): rb_w32_map_errno is not found on Ruby-3.1.0
- I faced Fiddle::DLError such following.
```
C:/hostedtoolcache/windows/Ruby/3.1.0/x64/lib/ruby/3.1.0/fiddle/import.rb:297:in `import_function': cannot find the function: rb_w32_map_errno() (Fiddle::DLError)
from C:/hostedtoolcache/... -
- https://github.com/ruby/tmpdir/commit/40107b59b3
-
- https://github.com/ruby/net-http/commit/843d4548de
-
- https://github.com/ruby/find/commit/0ebbd5b852
-
- https://github.com/ruby/zlib/commit/5f23cd3009
-
-
- https://github.com/rubygems/rubygems/commit/c29cd23826
-
10:58 AM Revision b633c9ac (git): Reduce p_args rules with p_rest
-
- palkan (Vladimir Dementyev) wrote in #note-6:
> jeremyevans0 (Jeremy Evans) wrote in #note-2:
> ...
Here is a PR: https://github.com/ruby/ruby/pull/5426 -
- jeremyevans0 (Jeremy Evans) wrote in #note-2:
> I don't think it's a bug that pattern match only supports setting local variables. However, I agree that it would be a useful feature for pattern match to support setting instance variabl... -
- baweaver (Brandon Weaver) wrote in #note-4:
> While we're in that domain where would we want to draw the line? Globals, constants, class variables?
> ...
I think, the phrase "variable assignment" draws a line here: any variable (local,... -
07:17 AM Feature #18408: Allow pattern match to set instance variables
- jeremyevans0 (Jeremy Evans) wrote in #note-2:
> I don't think it's a bug that pattern match only supports setting local variables. However, I agree that it would be a useful feature for pattern match to support setting instance variabl... -
08:55 AM Bug #18471: Regex#match(re, position) with start of a string anchors ^ and \A
- `\G` matches.
```ruby
str = "hello world"
/\Gworld/.match(str, 6)
``` -
08:54 AM Bug #18471: Regex#match(re, position) with start of a string anchors ^ and \A
- > I [...] expect [...] staring from position 6 in “hello world” [to] be equivalent to staring with position 0 in [the sub-]string “world”
I do not think so. Moving "the position in the string to begin the search" does not mean the strin... -
08:14 AM Bug #18471 (Rejected): Regex#match(re, position) with start of a string anchors ^ and \A
- Found this. Is it a bug in `Regex#match(re, position)`?
From `Regex#match` docs
> If the second parameter is present, it specifies the position in the string to begin the search.
```rb
str = "hello world"
/^world/.match(str, 6... -
- ```
compiling ../ruby.c
../ruby.c:1547:17: error: implicit declaration of function 'setup_yjit_options' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
setup_yjit_options(s, &opt->yjit);
^
../r... -
-
07:46 AM Bug #18470 (Closed): Union of two identical sets produces a set with duplicate members
-
- > `Set#reset`
Ah, that's the rehash equivalent I didn't see.
Yeah, I think we can close. -
01:18 AM Bug #18470: Union of two identical sets produces a set with duplicate members
- Doesn't the following from https://bugs.ruby-lang.org/issues/16996 address this issue?
> ...
> ...
It seems like this is not a bug and the outcome is expected without a call to `Set#reset`:
```ruby
C = Struct.new :id
a = Set.new
... -
01:08 AM Bug #18470: Union of two identical sets produces a set with duplicate members
- > The main problem is that `Set` doesn't expose a `rehash` method, so there's not really any way to workaround it. Maybe it should?
The rehash works. Should `add` also have a rehash?
```ruby
C = Struct.new :id
a = Set.new
f = C... -
05:46 AM Feature #18136: take_while_after
- I'd rather choose an obvious name, like `take_until_after`.
-
-
- Removed at https://github.com/ruby/ruby/commit/bf97415c02b11a8949f715431aca9eeb6311add2
-
-
01/10/2022
-
- Supporting Windows is in the plans, but as my colleagues have said it's fairly tricky as it could add a fair bit of complexity in several places. We're hoping to potentially migrate the YJIT codebase to Rust, which would give us more too...
-
- Treats:
#pread
#pwrite
#binmode
#binmode? -
- So it's indeed a rehash issue: https://github.com/casperisfine/set/commit/40ff2f907118d8766217bbe8ac27119111050217
Also it seems @marcandre knew about this case (or similar), based on the description of the issue I linked.
The main... -
- The tricky part is that the object is mutated after being inserted, so it's sounds like a rehash no longer happens, possibly because of https://bugs.ruby-lang.org/issues/16996.
It may or may not be considered a bug, I'll see what it wou... -
- We came across an issue where the union of two identical sets produced a non uniq Set.
We noticed this when upgrading from 2.7.1 to 3.1
See the attached test, the last assertion fails
``` ruby
C = Struct.new :id
a = Set.new
b... -
- Treats:
#sysseek
#syswrite
#sysread -
09:10 PM Revision 9e79ae53 (git): [ruby/reline] Clear dialog when just_move_cursor is called with dialog at last line
- https://github.com/ruby/reline/commit/05024b968e
-
- By the way, even calling `write` directly is no guarantee of synchronous output between threads/processes - on Linux there is an informal guarantee of page-sized atomicity.
-
- Thanks for all that information.
This is a bug fix, but what you are proposing sounds like a feature request.
I want to merge this bug fix, but I think we should consider the direction you propose. I'm happy to raise this point at ... -
- ioquatix (Samuel Williams) wrote in #note-6:
> The current implementation before and after this PR makes no such guarantee unfortunately. The best you can do as a user is buffer your own string and call write with that as an argument to... -
- This adds support for passing keyword arguments to cfuncs. This is done
by calling a helper method to create the hash from the top N values on
the stack (determined by the callinfo) and then moving that value onto
the stack. -
- Revises much of the introductory material.
Also treats:
#close_on_exec
#close
#closed?
#close_read
#close_write -
05:02 PM Revision 04d9b6d2 (git): [DOC] Link to Ruby Spec and rephrase project goal
- The word "specification" can be confusing as it might make readers
assume that the Ruby Spec Suite is a specification similar to an ISO
specification. Avoid the word and link to the project so curious parties
could read more about the pr... - 03:30 PM Revision c9325cb8 (git): * 2022-01-11 [ci skip]
-
-
-
- byroot (Jean Boussier) wrote in #note-4:
> @jeremyevans thanks for the fix. Do you think we should mark this as a 3.1 backport?
Sure, that makes sense to me.
-
- @jeremyevans thanks for the fix. Do you think we should mark this as a 3.1 backport?
-
-
- Thanks, merged.
-
12:04 PM Revision b4d0d07e (git): Clarify ractor documentation meaning and formatting.
-
- https://github.com/ruby/ruby/blob/ruby_3_1/NEWS.md#mjit says
```
The default --mjit-max-cache is changed from 100 to 10000.
```
But `ruby --help` says 100 yet.
So I think https://github.com/ruby/ruby/commit/c764e368bd9c0487e6cc9... - 11:18 AM Revision 7b5d49a0 (git): * 2022-01-10 [ci skip]
-
- changed at 028f1887c2bfa50dcfc1b623470d6ab1b880fdde
-
05:35 AM Bug #18468 (Closed): Tutorial Link for Optionparser is broken
- If one happens to go to this page for viewing documentation for [OptionParser ](https://docs.ruby-lang.org/en/master/OptionParser.html). The link for seeing the [tutorial](https://docs.ruby-lang.org/en/master/doc/optparse/tutorial_rdoc.h...
01/09/2022
-
- > I think it'd better to guarantee atomicity for puts and write, even if the same fd is used by multiple IO instances, and even if the same fd is used by multiple processes.
The current implementation before and after this PR makes no... -
- Ah and in either case the IO scheduler should either receive the already-concatenated string, or all strings to write together in a single hook call.
Calling the write hook for each argument is of course broken. -
- I think it'd better to guarantee atomicity for `puts` and `write`, even if the same fd is used by multiple IO instances, and even if the same fd is used by multiple processes.
The write lock does not address both of these cases and it's... -
- Even though `stderr` should not be buffered, I feel like it would be advantageous to use a write lock too, to avoid interleaved log output if possible. Obviously still an issue for multi-process all logging to the same `stderr`.
-
- I tried to make a micro-benchmark measuring this.
```
> make benchmark ITEM=io_write
/Users/samuel/.rubies/ruby-3.0.3/bin/ruby --disable=gems -rrubygems -I../benchmark/lib ../benchmark/benchmark-driver/exe/benchmark-driver \
... -
- As part of working through the implementation, I merged <https://github.com/ruby/ruby/pull/5418>.
The follow up PR, making `io_binwrite` and `io_binwritev` atomic, is here: <https://github.com/ruby/ruby/pull/5419>. -
- Right now, `IO#write` including everything that calls it including `IO#puts`, has a poorly specified behaviour w.r.t. other fibers/threads that call `IO#write` at the same time.
Internally, we have a write lock, however it's only used... -
- The language around what makes an extension Ractor safe could use a little clarification.
The PR for this issue is https://github.com/ruby/ruby/pull/5421. -
- This reverts commit 9ad34da47ff7d71446e667897559047ed5635b60, as
`RBOOL` is not defined publicly yet. -
- It's third party's issue. https://github.com/typhoeus/ethon/issues/193
-
06:36 AM Bug #18466 (Third Party's Issue): Im receiving an error when attempting to download RealmSwift Pods
- I was attempting to install the RealmSwift Pods. I received the following error during the installation. This was in terminal.
jeremiahdepass@Jeremiahs-Air Pod % pod install
Analyzing dependencies
/Library/Ruby/Gems/2.6.0/gems/eth... -
-
-
- `--yjit-call-threshold` and `--yjit-max-versions` need an argument.
-
01/08/2022
- 11:06 PM Revision 86484575 (git): Don't combine test-all and rubyspec.
-
- This reverts commit c365c5921ea26e31c03a85b01ff4c04629abfc10.
- 07:41 PM Revision a5fffb31 (git): * 2022-01-09 [ci skip]
-
- This adds support for cfuncs which take variable arguments using a Ruby
array. This is specified with the method entry's argc == -2. -
- Saving SP later allows us to avoid storing SP in an intermediate
register and allows using the ctx_stack_opnd helpers. -
- Solaris requires that the pointer errret_int is alined to an integer,
however, with VWA, strings are no longer aligned to an integer, so use a
Fiddle::Pointer with a malloc'd region instead.
https://github.com/ruby/reline/commit/5fcd89ab0c - 11:03 AM Revision 0ca00e2c (git): Move IO write buffer allocation into function.
-
-
04:37 AM Bug #18464 (Closed): RUBY_INTERNAL_EVENT_NEWOBJ tracepoint causes an interpreter crash when combined with Ractors
- When a Ractor is created whilst a tracepoint for `RUBY_INTERNAL_EVENT_NEWOBJ` is active (registered with `rb_tracepoint_new`/`rb_tracepoint_enabled`), the interpreter crashes with a null pointer dereference with the following backtrace:
... -
- That gem seems pretty old, before `include/ruby/random.h` was introduced.
You can see a skeleton at `ext/-test-/random/loop.c` too. -
-
-
-
-
- Routines that are called from YJIT's output code can call methods, and
calling methods mean they can capture and change the environment of the
calling frame.
Discard type info whenever we perform routine calls. This is more
conservative...
01/07/2022
-
-
- Improve rb_raw_obj_info to output additional into about strings
including the length, capacity, and whether or not it is embedded. -
-
06:23 PM Feature #12125: Proposal: Shorthand operator for Object#method
- Has `&&` been considered?
```
Dir["*/*.c"].map(&&File.basename)
```
It can also adapt to outside usage so `&File.basename` equals `File.method(:basename)`.
-
- I'm not fully clear on the expected semantics of private/protected/public in a subclass, that would probably be good to improve in the docs of these methods or in general docs.
However since the current semantics seems to clearly create... -
- bughit (bug hit) wrote in #note-9:
> V8 handles that, detecting eval and deopting, so ruby can too.
So what does V8 do then if `eval` is aliased e.g., to `e`?
---
BTW, your replies feel rather aggressive to me.
You are speakin... - 03:50 PM Revision a1bef7c2 (git): * 2022-01-08 [ci skip]
-
- After changing the encoding, we should update the terminator length.
-
03:01 PM Bug #12666: Fatal error: glibc detected an invalid stdio handle
- I can see the patch https://github.com/ruby/fiddle/commit/a267a40be7844224c5f000530bd3e8e906f1acea is applied into the Ruby 3.0 stable branch ruby_3_0 and Ruby 3.0.3 as a part of upgrading the fiddle to 1.0.8 by the following commit.
ht... -
- Let me explain more context about this backport requests.
Here is current `test/fiddle/helper.rb` file on ruby/ruby ruby_2_6 branch.
https://github.com/ruby/ruby/blob/02c341c9bc5879eae568ed2ba02cf227ed948199/test/fiddle/helper.rb#L... -
-
09:25 AM Feature #17473: Make Pathname to embedded class of Ruby
- For what it's worth, although for unrelated reasons, I completely rewrote `Pathname` in pure Ruby here: https://github.com/rubygems/rubygems/pull/4992.
-
07:11 AM Feature #18463: Random number generation with xoshiro
- Thanks for the feedback. Another good algorithm is pcg https://rubygems.org/gems/pcg_random
-
06:55 AM Feature #18463: Random number generation with xoshiro
- I guess you can start implementing xoshiro as a separate gem now. I remember @mrkn once wanted to implement xorshift, and `include/ruby/random.h` was introduced (mainly) for that purpose. Not sure his current status though.
-
- Xoshiro https://prng.di.unimi.it/ random number generation is typically faster than Mersenne Twister currently used in Ruby in https://github.com/ruby/ruby/blob/master/random.c It would be good to allow use of xoshiro either as an opti...
-
- * [Feature #18462] Proposal to merge WASI based WebAssembly support (mame)
* Let's support wasm. This will allow MRI to work on browsers and edge computing platforms. -
06:10 AM Feature #18462 (Closed): Proposal to merge WASI based WebAssembly support
- # Proposal to merge WASI based WebAssembly support
This is an initial port of WASI based WebAssembly support.
This enables a CRuby binary to be available on Web browser, Serverless Edge environment, and other WebAssembly/WASI embedde... -
-
-
- Fixes [Bug #18158]
https://github.com/ruby/pathname/commit/914c726aa2 -
- I've submitted a pull request to fix this error: https://github.com/ruby/irb/pull/325
-
- Get rid of depending on using $/ internally in String#chomp!, and
chomp the separator at once. -
- Get rid of depending on using $/ internally in ARGF.gets.
01/06/2022
-
11:13 PM Feature #18461: closures are capturing unused variables
- > That's of no use then, that's just not the semantics of Proc#binding, which is to capture every variable at the place the block is defined.
If you are suggesting that everything is set in stone, that's obviously false. Changes can b... -
- bughit (bug hit) wrote in #note-4:
> There's no such need. If the capture is optimized then Proc#binding will continue giving access to what has been captured, rather than everything that could be captured.
That's of no use then, tha... -
- > uncaptured ones are on the stack and disappear with the stack frame. You can't get them back later.
That's actually one of the major benefits of optimized capture, you're not wasting memory holding on to things you don't need. There... -
- > However, as soon as you call proc.binding.local_variables, you should see all local variables in scope (deoptimizing if necessary)
That's not possible. Captured variables are on the heap, uncaptured ones are on the stack and disappe... -
- bughit (bug hit) wrote in #note-4:
> > But, maybe we could deprecate Proc#binding and remove it, I think that would be a good start.
> ...
This is not how it should be implemented, IMO. Optimizing such procs is fine, as long as such o... -
- > But, maybe we could deprecate Proc#binding and remove it, I think that would be a good start.
There's no such need. If the capture is optimized then Proc#binding will continue giving access to what has been captured, rather than eve... -
- I think Ruby JIT implementers are already aware of this, but these are the current semantics of Ruby.
I think JRuby does some optimization like this (only keeps the outside scope if there is `binding/eval` inside the block, but JRuby ... -
- Interning string literals also breaks code, but it's worth moving in that direction, and here also.
Note the following quote from chromium/v8:
> The only solution I could think of is that whenever devtools is on, we would deopt all... -
- This is Ruby, you can always modify the value of the local variable later, even if it isn't accessed inside the proc itself.
Such access can affect other scopes:
```ruby
def foo
a = 1
[->{}, ->{}]
end
x, y = foo
x.binding... -
- This reverts commit 44368b5f8bc21e19fa06a0fc0625923fc41293e6.
-
- This reverts commit d4a95428bb244ca8c4a97ad50f3837f191f1f0c3.
-
- Regarding openat(), [4bf3cb5ba9c0242bd5a6d0d55b7db9f837c09edf](https://bugs.ruby-lang.org/projects/ruby-master/repository/git/revisions/4bf3cb5ba9c0242bd5a6d0d55b7db9f837c09edf) was 11 years ago, so I assume there is little demand or nee...
-
- I plan to make a PR to move Pathname back to Ruby for all methods which don't significantly gain from being written in C.
I'm coming from https://github.com/oracle/truffleruby/issues/2559, which is additional motivation for it, the curr... -
- Frozen strings should have the same termlen as the original string when
copy_encoding is true. -
- If we set encoding after the call to rb_str_buf_cat, then rb_str_buf_cat
will not set the correct terminator length. -
-
-
-
07:31 PM Feature #18438: Add `Exception#additional_message` to show additional error information
- 👋, I maintain [Datadog's application monitoring gem](https://github.com/DataDog/dd-trace-rb), alongside Ivo.
ivoanjo (Ivo Anjo) wrote in #note-3:
> I'll need to sync with my colleagues at Datadog and may take a few days because a lot... -
- some libc implementations (e.g. wasi-libc) define MREMAP_MAYMOVE, but
don't have mremap itself, so guard the use of mremap by HAVE_MREMAP -
- Treats:
#ungetc
#isatty
#close_on_exec? -
04:13 PM Revision 1bfccba7 (git): Add bugs.ruby links.
-
- Applied in changeset commit:git|a79c59472df38297c246b27713c277f2edaefa7a.
----------
Allow include before calling Module#initialize
This is to allow Module subclasses that include modules before
calling super in the subclass's initiali... -
- A simple work around for this is to `include` after calling `super`.
`initialize` checks whether the module is uninitialized, and fails otherwise. When calling `include`, the module is marked as initialized. If you call `include` be... - 04:03 PM Revision 818fc853 (git): * 2022-01-07 [ci skip]
-
- Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
-
-
- This is to allow Module subclasses that include modules before
calling super in the subclass's initialize.
Remove rb_module_check_initializable from Module#initialize.
Module#initialize only calls module_exec if a block is passed,
it do... - 02:58 PM Revision 73be7a85 (git): [rubygems/rubygems] Fix suggestions flag
- https://github.com/rubygems/rubygems/commit/b55a1393ca
- 02:58 PM Revision cea4a810 (git): [rubygems/rubygems] Let fetch understand gem:version syntax
- Fix version error message
Add tests to fetch error messages
Fix default version since is not necessary
https://github.com/rubygems/rubygems/commit/070620ebe4 -
- Before:
```
$ gem install sfdsfdsfsdide --force
ERROR: While executing gem ... (NoMethodError)
undefined method `spec' for nil:NilClass
@always_install << newest.spec
^^^^^
```
After:
```
$ gem i... -
11:13 AM Feature #18460 (Rejected): implicit self for .() syntax without rvalue
- This proposal is rejected for several reasons:
* we don't allow `.m` notation for implicit self (for now at least)
* You will gain only 4 fewer characters
* I don't think it's worth the cost of syntax complexity it brings
Matz.
-
09:33 AM Revision e3b0c8c1 (git): [ruby/reline] windows: test_yamatanooroti fix
- windows can't create too narrow and tall window.
https://github.com/ruby/reline/commit/20b5f2f6fc -
- 07:02 AM Revision 2db7952e (git): Update bundled gems list at 2022-01-06
-
-
-
01:36 AM Feature #12966 (Rejected): net/ftp to include fxp support?
- net/ftp is now a bundled gem, so I close this issue.
-
- RMODULE_SUPER is initialized to 0, as the uninitialized module
flag is used since b929af430c39df6597d2f3f53b82c38b1d76217b. -
- Because https://github.com/ruby/ruby/pull/5148 merged after Ruby 3.1.0 released.
13241b71a50dded0a7b021ec4f2fb6a995daace9 did not fix proc spec yet.
https://github.com/ruby/actions/runs/4718820699?check_suite_focus=true#step:18:173
```...