Activity
From 09/28/2024 to 10/04/2024
10/04/2024
-
10:45 PM Revision e766cb3e (git): Suppress warnings in `time_init_parse` function
- When building Ruby on Ubuntu 22.04 and GCC 11.4.0, the following warning appeared.
And this change has suppressed warning.
```
compiling ../ruby/time.c
../ruby/time.c: In function ‘time_init_parse’:
../ruby/time.c:2650:21: warning: comp... -
09:56 PM Revision 563263a9 (git): [ruby/reline] Concatenate some rendeing test
- (https://github.com/ruby/reline/pull/749)
https://github.com/ruby/reline/commit/41b54140f4 -
08:11 PM Revision 87169dd4 (git): [DOC] Tweaks for Array#none? (#11788)
-
-
08:01 PM Revision 648f558e (git): [rubygems/rubygems] Remove now unused realworld spec
- Signed-off-by: Samuel Giddins <segiddins@segiddins.me>
https://github.com/rubygems/rubygems/commit/2484267920 -
- Signed-off-by: Samuel Giddins <segiddins@segiddins.me>
https://github.com/rubygems/rubygems/commit/1ef33fa0af -
- Signed-off-by: Samuel Giddins <segiddins@segiddins.me>
https://github.com/rubygems/rubygems/commit/d8b5d05e46 -
- Signed-off-by: Samuel Giddins <segiddins@segiddins.me>
https://github.com/rubygems/rubygems/commit/300fb96ffc -
- Signed-off-by: Samuel Giddins <segiddins@segiddins.me>
https://github.com/rubygems/rubygems/commit/272f3464a3 -
- Signed-off-by: Samuel Giddins <segiddins@segiddins.me>
https://github.com/rubygems/rubygems/commit/085bafd8d4 -
- Signed-off-by: Samuel Giddins <segiddins@segiddins.me>
https://github.com/rubygems/rubygems/commit/06eec6d855 -
- 3.0 has been EOL since march, drop support for it before the 3.4 release is cut
Signed-off-by: Samuel Giddins <segiddins@segiddins.me>
https://github.com/rubygems/rubygems/commit/fc1f03b06a -
07:04 PM Revision 30038656 (git): Fix intermediate array off-by-one error
- Co-authored-by: Adam Hess <HParker@github.com>
-
05:36 PM Revision f77517f4 (git): [DOC] Minor adjustment for Array#min
-
-
-
- https://github.com/ruby/prism/commit/51f2df60ff
-
04:25 PM Feature #15554: warn/error passing a block to a method which never use a block
- > generic group name that can be used for other future warnings
> ...
I agree with both of the above; they are both desirable features to have in a warning system.
At the same time let's keep in mind that the existing categories are pre... -
02:02 PM Feature #15554: warn/error passing a block to a method which never use a block
- byroot (Jean Boussier) wrote in #note-69:
> I thought we were looking for a generic group name that can be used for other future warnings that may have false positives.
I think it's necessary to be able to enable/disable specific one... -
01:10 PM Feature #15554: warn/error passing a block to a method which never use a block
- I thought we were looking for a generic group name that can be used for other future warnings that may have false positives.
-
- I think `Warning[:strict_unused_block]` is good.
> What we really want to convey is that this group of warnings is more likely to have false positives.
Yes, but also it removes the not-fully-precise heuristic of "if any method with... -
- byroot (Jean Boussier) wrote in #note-66:
> "strict" works I suppose. What we really want to convey is that this group of warnings is more likely to have false positives.
Warning[:strict_unused_block]
Warning[:possible_unused_block]... -
- "strict" works I suppose. What we really want to convey is that this group of warnings is more likely to have false positives.
-
12:45 PM Feature #15554: warn/error passing a block to a method which never use a block
- I don' like the term "pedantic" either. How about "strict"? I mean `--warn-strict-unused-block` or `Waning[:strict_unused_block]`.
Matz.
-
- https://github.com/ruby/prism/commit/80cd335222
-
03:43 PM Misc #20774: Remove remaining locale dependent code from Windows port
- I opened https://github.com/ruby/ruby/pull/11799 to implement this issue.
-
- rb_gen_ivtbl_get locks the VM, but the VM must be locked during marking
so we can directly read from the generic_ivtbl without locking the VM. -
12:47 PM Misc #20728: Propose Eileen Uchitelle as a core committer
- Email send and PR opened here https://github.com/ruby/git.ruby-lang.org/pull/84
Thank you! -
- Sounds good, will do!
-
05:17 AM Misc #20728 (Assigned): Propose Eileen Uchitelle as a core committer
- @eileencodes Can you read [this](https://github.com/ruby/ruby/wiki/Committer-How-To#how-to-register-you-as-a-committer) and give your information to me?
@kddnewton Please mentor Eileen especially Feature request, Backport request and ... -
-
09:57 AM Bug #20783: --enable-shared and the rpath/runpath are broken on Linux on CRuby master
- https://github.com/ruby/ruby/pull/11797
-
- BTW this also shows the ruby/ruby CI does not currently test an installed ruby with `--enable-shared`.
It seems important to add a test to avoid such regressions. -
- https://github.com/ruby/ruby-dev-builder/actions/runs/11095200420
```
$ ruby test_files/cli_test.rb
ruby: error while loading shared libraries: libruby.so.3.4: cannot open shared object file: No such file or directory
```
And inde... -
-
- I prepared to sync `ruby/ruby` and `ruby/win32-registry`.
I found some question for your changes. Can you look https://github.com/ruby/win32-registry/pull/5 ?
- 08:25 AM Revision 86e8a36e (git): Revert "Direct access to `fptr->fd` should prefer to use the `internal/io.h`. (#11793)"
- This reverts commit 6ea0dcc9781931129e77540097712f6196d49fde that was accidentally merged.
- 07:44 AM Revision 6ea0dcc9 (git): Direct access to `fptr->fd` should prefer to use the `internal/io.h`. (#11793)
- 07:35 AM Revision c33cb9a5 (git): Update `io_spec.c` to use `rb_io_maybe_wait*` if possible. (#11792)
- 06:36 AM Revision c878843b (git): Better handling of timeout in `rb_io_maybe_wait_*`. (#9531)
-
05:57 AM Feature #20782 (Closed): Introduction of Happy Eyeballs Version 2 (RFC8305) in TCPSocket.new
- This is an implementation of Happy Eyeballs version 2 (RFC 8305) in `TCPSocket.new`.
See https://github.com/ruby/ruby/pull/11653
### Background
Prior to this implementation, I implemented Happy Eyeballs Version 2 (HEv2) for `Socket.... - 05:40 AM Revision 96d69d2d (git): Clarify `rb_io_maybe_wait` behaviour. (#9527)
-
- This proposal has been approved by @akr. I merged https://github.com/ruby/ruby/pull/3705 now.
- 03:22 AM Revision 939ec9f0 (git): Bump github/codeql-action from 3.26.10 to 3.26.11
- Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.26.10 to 3.26.11.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.... -
-
03:21 AM Revision 3c54b8e9 (git): Allow method chaining with Pathname#mkpath
- Currently in my code when I want to create a pathname object and create a path at the same time I must use tap
```
path = Pathname.new("/tmp/new").tap(&:mkpath)
```
I think it would be cleaner to be able to chain on the results of thes... -
- This feature request has been approved by @akr. I merged https://github.com/ruby/ruby/pull/3709 now.
-
- When I want to create a tmpdir I often want to manipulate it as a pathname. By introducing Pathname.mktmpdir I can get this behavior.
Currently I must:
```ruby
Dir.mktmpdir do |dir|
dir = Pathname(dir)
# ... code
end
```
I would l... -
- `Pathname#touch` is rejected at [this reason](https://bugs.ruby-lang.org/issues/7361#note-5).
I asked this proposal to @akr again, he is still negative for `Pathname#touch`. - 01:09 AM Revision 3d4d5c8d (git): Add `IO::Buffer` tests for read and write with length & offset.
- 01:09 AM Revision bc482e63 (git): Fix size calcuation when offset is given + updated documentation.
-
- Thank you. I confirmed that.
10/03/2024
-
09:55 PM Feature #20770: A *new* pipe operator proposal
- Has *"then"* but as a keyword been considered?
In the basic version it could appear as a *"begin..then..end"* block:
``` ruby
value = begin add value, 3 then square it then half it end
```
It looks like syntax highlighting is ready. *"b... -
- The return value of Array#max is the maximum value per the block, not
from the block. -
-
08:20 PM Revision 8e7df4b7 (git): Rename size_pool -> heap
- Now that we've inlined the eden_heap into the size_pool, we should
rename the size_pool to heap. So that Ruby contains multiple heaps, with
different sized objects.
The term heap as a collection of memory pages is more in memory
managem... -
- After the individual tomb_heaps were removed in favour of a global list
of empty pages, the only instance of rb_heap_t left is the eden_heap
within each size pool.
This PR inlines the heap fields directly into rb_size_pool_t to remove
i... -
-
- https://github.com/ruby/prism/commit/7a0af49997
-
- https://github.com/ruby/prism/commit/5dd36b979e
-
04:04 PM Bug #20433 (Closed): Hash.inspect for some hash returns syntax invalid representation
- Yes, I have merged it since @matz said at the dev meeting today that he still wants to try this change in the next preview release. So closing.
However, it may be reverted if the impact of the incompatibility is too large. -
- @tompng @mame what is the status on this? I see https://github.com/ruby/ruby/pull/10924 has been merged, should this ticket be closed?
I personally love this change, but I have a lot of tests to update as a result, so I'd like to know... -
-
- (https://github.com/ruby/reline/pull/747)
https://github.com/ruby/reline/commit/7534f7f92a -
-
02:27 PM Bug #20620 (Closed): singleton_method undefined for module using "extend self"
- Applied in changeset commit:git|9986a7c3930437bc9d9b88736c22695585aa6c48.
----------
Make Object#singleton_method return methods in modules included in or prepended to singleton class
To simplify the implementation, this makes Object#s... -
- @jeremyevans0 Thank you. Let us merge the pull-request, and experiment with the preview.
Matz.
-
- To simplify the implementation, this makes Object#singleton_method
call the same method called by Object#method (rb_obj_method), then
check that the returned Method is defined before the superclass of the
object's singleton class. To ke... -
-
-
12:52 PM Revision 66124cdb (git): [ruby/prism] Use `partial_script` for the parser translators
- Followup to https://github.com/ruby/prism/pull/3079
https://github.com/ruby/prism/commit/68f434e356 -
- Thank you. I added owner grant.
-
- I added `repl_type_completor` at https://github.com/ruby/ruby/commit/50b32a3c9206df2ec7bcb4c54a59844c27f1c144
@tompng Can you add owner grant of https://rubygems.org/gems/repl_type_completor to me? I will not release without maintaine... -
- I'll support this.
-
- Accepted. Looking forward to making it public.
Matz.
-
-
-
09:46 AM Feature #20669: Add Marshal::MarshalError class to differentiate ArgumentErrors
- In the meantime, Dalli merged a change that sounds a lot like Eregon's comment. https://github.com/petergoldstein/dalli/pull/1011
My immediate needs are met, and I will close this feature request. EDIT: I can't find a button to close th... - 12:29 PM Revision cd96af2c (git): Add `IO::Buffer` tests for read and write with length & offset. (#11779)
-
- (https://github.com/ruby/rdoc/pull/1184)
https://github.com/ruby/rdoc/commit/7b68545094 -
-
- (https://github.com/ruby/reline/pull/753)
https://github.com/ruby/reline/commit/9230fe162d -
- # The next dev meeting
**Date: 2024/11/07 13:00-17:00** (JST)
Log: https://github.com/ruby/dev-meeting-log/blob/master/2024/DevMeeting-2024-11-07.md
- Dev meeting *IS NOT* a decision-making place. All decisions should be done at t... -
-
-
-
-
-
-
-
- It was discussed at the dev meeting.
`File.chmod` and `FileUtils.chmod` have an incompatibility in their handling of symbolic links: `File.chmod` changes the permissions on the target of the symbolic link, while `FileUtils.chmod` chan... -
09:11 AM Feature #20705: Should "0.E-9" be a valid float value?
- @nobu Could you open a PR based on your implementation https://github.com/nobu/ruby/tree/float-dtoa ?
My implementation doesn't accept `0xf.p0` but your implementation does. -
- I'd like to enhance string to float conversion in general. I might introduce small incompatibility, but impact will be small.
Matz. -
09:10 AM Bug #20693: Dir.tmpdir should perform a real access check before warning about writability
- I think the reason why `File.writable?` is used should be described in the source.
-
- 08:41 AM Revision 2c0149d3 (git): Update bundled gems list at 6435dfce5fcddd22d3570eda2c60cc [ci skip]
-
-
-
- I don't want to add a special value (Hash::DROP) nor special syntax (?key:) here. Use `h = {foo: 1}; h[:bar] = 2 if bar?`.
Matz.
- 07:00 AM Revision 7f251ce5 (git): Update bundled gems list as of 2024-10-03
-
- I have been merged https://github.com/ruby/singleton/pull/4
- 06:04 AM Revision 1b3f18af (git): each_address should now resolve for AAAA first
- AAAA over A is standards track behaviour as per RFC 6724.
-
- Rather than checking the class we can check the type.
This is very subtly different for String subclasses, but I think it's
OK.
We also save on checking the type again in the fast path.
https://github.com/flori/json/commit/772a0201ab -
- On my `JSON.dump` benchmark it shows up as 6% of runtime, compared
to 40% for `convert_UTF8_to_JSON`.
Since the vast majority of the time this function is called we
still have some buffer capacity, we might as well check that
first and ... -
- Given that we called `rb_enc_str_asciionly_p`, if the string encoding
isn't valid UTF-8, we can't know it very cheaply by checking the
encoding and coderange that was just computed by Ruby, rather than
to do it ourselves.
Also Ruby migh... -
- OK, welcome Eileen.
Matz.
-
- OK, I accept to make `rb_thread_call_with_gvl` to acquire GVL only when needed. @ko1 worried it may encourage bad design pattern, but not allowing `rb_thread_call_with_gvl` with GVL does not improve the situation.
So I accept it, you ha... - 04:11 AM Revision 835ac8a4 (git): Update bundled gems list at a048090bd591ef874f36effb2065d6 [ci skip]
-
-
- I confirmed this to @akr again. He said "rfc3339 is slightly different from iso8601. I don't want to introduce this alias".
-
-
- `PTY.spawn` with a block detaches the spawned process and leaves it
running in background even after exiting the given block. It is the
responsibility of the caller to clean up the yielded IOs and PID.
https://github.com/ruby/ruby/acti... - 02:33 AM Revision 75c4ac33 (git): Update `IO::Buffer` documentation. (#11737)
- Update documentation.
-
12:40 AM Revision e5c26b0f (git): Stop skipping broken tests
-
10/02/2024
-
11:53 PM Bug #20780 (Open): related to #20779 -- crash creating large number of concurrent-ruby promises
- The attached script crashes (vs. the hang in issue #20779). I believe this is also a OSX specific resource issue, but have been unable to craft a better script to demonstrate the problem.
I've included a script to reproduce, the st... -
- Thread.new will hang the ruby process once past the OSX limit. It does not appear that's possible to trap and rescue failed thread creation.
It seems the Mac has a limit to the number of threads it supports and googling the issue sug... -
11:20 PM Feature #17326: Add Kernel#must! to the standard library
- Looks like PR was opened at https://github.com/ruby/ruby/pull/11772.
-
09:33 PM Revision e7734615 (git): [rubygems/rubygems] Remove compatibility code with old RubyGems
- https://github.com/rubygems/rubygems/commit/f11e42a3c5
-
- > OK, I'll revert all related changes if that's what you said that. I'm considering how to suppress needless warning with your request, But I can't collaborate with your tone.
I don't see anything wrong about @Earlopain 's tone. And h... -
- the mark_function_data callback was moved from the ractor to the VM.
-
-
- https://github.com/ruby/prism/commit/f29ceae5cf
-
- When gem repl_type_completor is installed, `irb --type-completor` will provide better completion in IRB.
~~~
irb(main):001* [1, 2, 3].map(&:ch█
|:chr|
~~~
~~~
irb(main):001* [1, 2, 3].map(&:chr).each ... -
-
05:47 PM Revision 2f5ab4c4 (git): YJIT: Merge `impl VALUE` blocks [ci skip]
- Reported by Kevin Menard.
-
- (https://github.com/ruby/reline/pull/748)
https://github.com/ruby/reline/commit/bf0f8fa333 -
- (https://github.com/ruby/reline/pull/750)
https://github.com/ruby/reline/commit/dd4a654e5d -
-
05:03 PM Feature #20770: A *new* pipe operator proposal
- @AlexandreMagro I don’t think this analogy is suitable here.
Of course, there are operators that aren’t convenient to use in chaining (though, I should admit to the sin of sometimes just using `the.chain.with.+(argument).like.that`, ... -
04:14 PM Feature #20770: A *new* pipe operator proposal
- zverok (Victor Shepelev) wrote in #note-28:
> What would `|>` bring here?
> ...
I’d like to turn the question around and ask what would be returned from the following code?
```ruby
array_a = [{ name: 'A', points: 30 }, { name: 'B', poin... -
03:19 PM Feature #20770: A *new* pipe operator proposal
- I agree with @zverok and am not quite sold on the value of `|>` over the existing `.then{}` if we still have to explicitly specify implicit args like `it/_1/etc` (unlike elixir).
I am intrigued by the `.{}` syntax though but wish it did... -
- A couple of my counterpoints to `|>` (and towards `.{}`, if we do need syntax sugar in this place at all):
While `|>` sure exists in other languages, we need to look into how it plays with the rest of the code/semantics of _our_ langu... -
- What's happening with the error message is that it's seeing the `$g` and determining that it's not a valid pattern, so it assumes the pattern is missing. Then it's determining that there is no statement delimiter (newline or semicolon) b...
-
- The same code ~~segfaulted~~ crashed due to "Unexpected node type" in 3.3.
Probably some backports are needed. -
- Syntax error is fine, but is really expecting end-of-input there?
```
$ ruby -v -e '1 => $g'
ruby 3.4.0dev (2024-10-01T14:59:58Z master 169a5ee99e) +PRISM [arm64-darwin23]
-e:1: warning: possibly useless use of a variable in void c... -
- The `RUBY_DESCRIPTION_WITH` macro has been removed already, so there
are no more descriptions strings with rjit/yjit enabled. -
-
-
- Note the last garbages.
```shell-session
$ ruby3.3 -W0 --yjit --parser=prism -e 'p RUBY_DESCRIPTION'
"ruby 3.3.5 (2024-09-03 revision ef084cc8f4) +YJIT +PRISM [arm64-darwin\x00\x00\x00"
```
commit:76ea5cde2a0f4834a5228104249b6b3... -
- https://github.com/ruby/prism/commit/aee2de91a3
-
-
-
-
- https://github.com/ruby/prism/commit/ab9d80987a
-
- I opened a pull request to merge nobu's and my tests together: https://github.com/ruby/win32-registry/pull/3
@hsbt You left me as the only maintainer for win32-registry. Is it expected that I maintain this library from now on?
How ab... -
- > The test file in https://github.com/larskanis/win32-registry seems quite different from the one in ruby/ruby.
Oh this is new! I created the win32-registry repository 10 months ago, when your test wasn't written. So I wrote my own. I... -
- The test file in https://github.com/larskanis/win32-registry seems quite different from the one in ruby/ruby.
Is it intentional? -
- Thanks! I transferred it to https://github.com/ruby/win32-registry. I keep you as admin on ruby/win32-registry.
-
- @hsbt I had to move the repository to an organization, in order to give you admin access. The new address is: https://github.com/oneclick/win32-registry
-
- @larskanis Thanks to invite me for https://github.com/larskanis/win32-registry. But I can't see `Settings` tab yet. Can you make me `admin` of that repository?
I consider to extract `net-http-sspi` from `win32/sspi` with nobu because ... -
- >My intention is that the repository can be moved to https://github.com/ruby/win32-registry and can be integrated it into ruby.
Can you add my GitHub account (hsbt) to that repository as admin? After that, I will transfer to under the... -
- >win32-registry
I agreed your proposal.
@nobu Do you have any concern?
> ...
I'm +1 to @nobu's opinion. we should remove it from `ruby/ruby`.
>win32-resolv
As nobu said, we already bundled it to resolv gem.
-
- ### win32/sspi
I'd propose to just drop it.
It has been unmaintained for years, not only `A` you mentioned (e.g., `Fixnum`), but no body noticed it.
### win32/resolve
it is included in [ruby/resolv](https://github.com/ruby/resolv) ... -
-
-
- During compilation, we write keyword default values into the iseq, so we
should mark it to ensure it does not get GC'd.
This might fix issues on ASAN like
http://ci.rvm.jp/logfiles/brlog.trunk_asan.20240927-194923
==805257==ERROR: ... -
-
- It's becoming tedious to map each format specifier to an argument.
-
- https://github.com/rubygems/rubygems/commit/0549ddbcc5
- 09:04 AM Revision 7469b830 (git): Update bundled gems list at bb97061f65d620b225d7638400642e [ci skip]
-
-
-
08:32 AM Revision fe8d7ca8 (git): [DOC] Alias Float#magnitude to abs
-
- The examples of chaining for other methods, such as #tap have the dot at
the start of the line, while #then has it at the end of the previous
line. Updated this to have consistent style in Kernel docs. -
-
- 05:36 AM Revision d2ec0e80 (git): [ruby/fiddle] test memory-view: ensure releasing in test
- It's for avoiding calling release on exit via GC. If it's happen, Ruby
will be crashed because Fiddle::MemoryView's finalizer may refer other
Ruby object. In exit phrase, the referred Ruby object may be already
freed.
https://github.com... - 05:36 AM Revision c9910851 (git): [ruby/fiddle] test: remove fragile memory leak tests
- https://github.com/ruby/fiddle/commit/0bfcd02bef
-
-
- https://github.com/rubygems/rubygems/commit/72d8d4dbba
-
- https://github.com/rubygems/rubygems/commit/47b7e50f64
-
- Gem command loading errors rely on `#to_s` on the raised exception, but
in the case of `MissingSpecVersionError` that was only the exception
name, making it printed twice and no message at all.
Before:
```
ERROR: Loading command: inst... -
- https://github.com/rubygems/rubygems/commit/95f60f0e60
-
- https://github.com/rubygems/rubygems/commit/517e9a8669
-
- https://github.com/rubygems/rubygems/commit/0a75590ac9
-
- https://github.com/ruby/singleton/commit/9d3c77a868
-
-
- (https://github.com/ruby/irb/pull/1007)
In debug command, IRB's context was using wrong binding.
Some code colorization, command detection failed because binding.local_variable returned wrong value.
https://github.com/ruby/irb/commit/6...
10/01/2024
-
- I strongly agree that new additions should be thoroughly evaluated and aligned with the philosophy of the language ("A programmer's best friend"). I've found the discussion so far to be very productive, and my opinion is that:
I don't... -
- [The Ruby-lang homepage](https://www.ruby-lang.org) states that Ruby has
> a focus on simplicity and productivity. It has an elegant syntax that is natural to read and easy to write.
And on the [about page](https://www.ruby-lang.org/en... -
- @Eregon this example (at least for me) is just an easy target for discussion (because it uses standard libraries, is easily reproducible, and demonstrates the multi-step realistic process that uses several libraries at once).
I believ... -
- One concern with so many `then {}` is that's a non-trivial overhead for execution (2 method calls + 1 block call for `then { foo(it) }` vs 1 method call for `foo(var)`).
So if it's added I think it should translate to the same as using ... -
- ufuk (Ufuk Kayserilioglu) wrote in #note-21:
> I tend to agree with @Dan0042 on this one, this seems to go against the nature of Ruby. In Ruby, an expression like `URI.parse(it)` is always eagerly evaluated, except when it is inside a b... -
05:19 PM Feature #20770: A *new* pipe operator proposal
- I think that this is one of the more interesting approaches to a pipeline operator in Ruby as it is just syntax sugar. As I am understanding it:
```ruby
foo
|> bar(_1, baz)
|> hoge(_1, quux)
```
would be treated by the parser t... -
05:09 PM Feature #20770: A *new* pipe operator proposal
- I tend to agree with @Dan0042 on this one, this seems to go against the nature of Ruby. In Ruby, an expression like `URI.parse(it)` is always eagerly evaluated, except when it is inside a block. This is not true in other languages; ones ...
-
- I'm not a big fan of this pipe operator idea, but at least the idea of using `it` is a good one; it solves many problems with previous proposals.
```ruby
foo = 42
1 |> foo |> BAR
#foo should be localvar but somehow is parsed as met... -
- vo.x (Vit Ondruch) wrote in #note-18:
> Right, this was far fetched and would not work admittedly. But that is why I proposed the `client_api_url.to(URI)`, because after all, this is IMHO mostly about type conversion. Why would I ever w... -
09:55 AM Feature #20770: A *new* pipe operator proposal
- zverok (Victor Shepelev) wrote in #note-17:
> I don’t think it is realistic, generally. I mean, convert every `f(g(x))` to “`x` should have method `g`, and the result should have method `f`, so you can write `x.g.f` always (or in most w... -
- vo.x (Vit Ondruch) wrote in #note-14:
> AlexandreMagro (Alexandre Magro) wrote in #note-7:
> ...
I don’t think it is realistic, generally. I mean, convert every `f(g(x))` to “`x` should have method `g`, and the result should have metho... -
- > We could expand the syntax to treat `.{}` as `.then{}`, similar to how `.()` is `.call()`.
I really like this idea. Yes, it is not “how it is in other languages” yet it has a deep internal consistency with other language elements a... -
- Not mentioning, the example ignores error handling, which would be IMHO the biggest problem in real life example
-
- AlexandreMagro (Alexandre Magro) wrote in #note-7:
To me it just demonstrates that the APIs are likely incomplete and don't provide methods for easy conversion. We have a lot of conversion methods such as `#to_str`, `#to_json`, ... Bu... -
- When pipeline operator was proposed previously (#15799), we briefly spoke of the idea of a block notation without a closing bracket ([the meeting log](https://github.com/ruby/dev-meeting-log/blob/c908bf7e7be60af5c5feabb544541de5f7d003ef/...
-
04:49 AM Feature #20770: A *new* pipe operator proposal
- FYI: https://github.com/tc39/proposal-pipeline-operator
is similar idea. -
-
-
- https://github.com/ruby/prism/commit/ccc746f918
-
- Many libraries bundled with ruby have been gemified and were separated into it's own repository.
Not so far the 3 win32 libraries: https://github.com/ruby/ruby/tree/master/ext/win32/lib/win32
* win32/registry
* win32/resolv
* win32/s... -
- ```ruby
a, c = [:a, :c].map { hash.delete(it) }
```
seems enough and does not require adding a new method for what looks like (to me) a narrow use case. -
- (https://github.com/ruby/reline/pull/751)
https://github.com/ruby/reline/commit/e9d4b37e34 -
-
02:59 PM Revision 169a5ee9 (git): Use user defined inline rules `user_or_keyword_variable`
-
- This should be addressed by https://github.com/ruby/ruby/pull/11711
-
- https://github.com/ruby/prism/commit/399ee28dc1
-
- https://github.com/ruby/prism/commit/498dd922d4
-
-
- Applied in changeset commit:git|86ae409467e3674c142f012ee3b2288b0305d87c.
----------
[Bug #20764] Refactor argument forwarding in lambda
Reject argument forwarding in lambda:
- without parentheses
- after optional argument(s) -
- Reject argument forwarding in lambda:
- without parentheses
- after optional argument(s) -
- Applied in changeset commit:git|35e124832e29b65c84d4e0e4e434616859f9bdf5.
----------
[Bug #20755] Frozen string should not be writable via IO::Buffer -
- The external_encoding of files, file names and ENV on Windows were changed from locale codepage to UTF-8 in ruby-3.0.
But there are still several remaining points where locale encoding is used although there is no need to do so.
The Wi... -
-
-
-
08:59 AM Revision 0f005449 (git): [ruby/singleton] Make compatible with Ruby 2.4
- https://github.com/ruby/singleton/commit/0a77bb492d
-
- https://github.com/ruby/singleton/commit/f31334a736
-
- https://github.com/ruby/singleton/commit/f684d36a47
-
- https://github.com/ruby/singleton/commit/1216a86303
-
- https://github.com/ruby/singleton/commit/ec4f66d9c1
-
-
-
- I'm not sure but this seems to need to be backported.
-
-
- 03:34 AM Revision 522614a3 (git): Bump github/codeql-action from 3.26.9 to 3.26.10
- Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.26.9 to 3.26.10.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.m... -
- https://github.com/ruby/ruby/pull/11736 fixed this.
09/30/2024
-
- jeremyevans0 (Jeremy Evans) wrote in #note-10:
> We could expand the syntax to treat `.{}` as `.then{}`, similar to how `.()` is `.call()`. With that, you could do:
> ...
The idea of using `.{}` is really creative, but it feels somewh... -
10:55 PM Feature #20770: A *new* pipe operator proposal
- AlexandreMagro (Alexandre Magro) wrote in #note-9:
> Yes, and it's also possible to achieve this with a chain of `.then`, which results in a similar structure. The idea of the pipe operator is to be syntactic sugar, bringing functionali... -
- ufuk (Ufuk Kayserilioglu) wrote in #note-8:
> You can also make the whole pipeline with just using procs:
> ...
Yes, and it's also possible to achieve this with a chain of `.then`, which results in a similar structure. The idea of the... -
- AlexandreMagro (Alexandre Magro) wrote in #note-7:
> With the pipe operator, the same logic can be simplified and made more readable:
> ...
I would like to note that this almost works already today:
```ruby
irb> client_api_url = "htt... -
- vo.x (Vit Ondruch) wrote in #note-6:
> Code like `add(value, 3)` is hardly some idiomatic Ruby. If it was Ruby, then you'd likely use `value.add(3)` or `value + 3`. Other examples of readable code are [here](https://poignant.guide/book/... -
- Code like `add(value, 3)` is hardly some idiomatic Ruby. If it was Ruby, then you'd likely use `value.add(3)` or `value + 3`. Other examples of readable code are [here](https://poignant.guide/book/chapter-3.html). I can't see what is rea...
-
- bkuhlmann (Brooke Kuhlmann) wrote in #note-4:
> For background, this has been discussed before:
> ...
One issue with `.pipe` is that it mixes two approaches: the object method chain (`lhs.rhs`) and passing the result as an argument (`r... -
02:15 PM Feature #20770: A *new* pipe operator proposal
- For background, this has been discussed before:
- [15799](https://bugs.ruby-lang.org/issues/15799): This was implemented and then reverted.
- [20580](https://bugs.ruby-lang.org/issues/20580): This recently popped up as well.
- There... -
- I would still love to see this type of pipeline functionality implemented with plain expressions instead of new operators.
I have this (old) working [proof of concept](https://github.com/lendinghome/pipe_operator#-pipe_operator) gem f... -
- nobu (Nobuyoshi Nakada) wrote in #note-1:
> In the previous trial syntax, the receiver of RHS was the result of LHS.
> ...
Exactly, this is the expected behavior of the pipe operator in other functional languages, such as Elixir. In th... -
- In the previous trial syntax, the receiver of RHS was the result of LHS.
In your proposal, the receiver of RHS is the same as LHS, and the LHS result is passed as an implicit argument?
-
11:00 PM Revision af63b4f8 (git): Return an Iterator Instead of a Vector in `addrs_to_pages` Method (#11725)
- * Returning an iterator instead of a vec
* Avoid changing the meaning of end_page
---------
Co-authored-by: Takashi Kokubun <takashikkbn@gmail.com> -
- Instead of calling rb_gc_event_hook inside of rb_gc_obj_free, it should
be up to the GC implementation to call the event. -
-
05:12 PM Revision d592ddd5 (git): Fix compile issue with a short-circuited if/unless condition and `defined?`
- This caused an issue when `defined?` was in the `if` condition. Its
instructions weren't appended to the instruction sequence even though it was compiled
if a compile-time known logical short-circuit happened before the `defined?`. The c... -
-
-
- https://github.com/ruby/actions/actions/runs/11095032727/job/30823174026#step:3:349
-
-
-
- Thank you — I have opened https://github.com/ruby/prism/pull/3096 to fix this.
-
- https://github.com/ruby/prism/commit/fd58d6a9ea
-
- https://github.com/ruby/ruby/pull/11738
-
- We don't need to create an empty string for interpolation unless it is
the only element.
For example:
"#{hello} world"
Before:
0000 putobject "" ( 1)[Li]
0002 putself
... -
12:22 PM Bug #20753: [doc] IO::Buffer examples try to write into readonly buffer returned from IO::Buffer.for
- https://github.com/ruby/ruby/pull/11737
-
- Looks like @nobu already made a PR here: https://github.com/ruby/ruby/pull/11735
-
- The second example `XameError` is hilarious, what a great bug. Yes, this should be fixed.
-
-
- 8350b48cfa7d344d9e2dc9748c26607c1b89d7df introduced a memory leak bug.
Will fix [Bug #20773]
`loop { File.realpath("foo") }` caused memory leak. -
- expanded
(https://github.com/ruby/rdoc/pull/1181)
Something that's been bothering me is that while the source code is
not visible by default, the browser still jump to it when searching.
Adding the `visible` property prevents this.
Tes... -
-
- We should stop warnings at some point. I decided to that period EOL-ed versions.
ex. In 2024, Ruby 3.0 is EOL. we removed webrick, rexml, rss from warning targets. -
- I apologize for my tone, I will try to be more understanding. I am just a bit frustrated with the warnings in general, especially with the ones that were backported 3.3.5. I know it is already reverted but they do still happen now.
It... -
- >All it does is supress the warning from reline (which is suppressed directly in the gem right now anyways) when fiddle is gone in 3.5
Yes, I only accept that point with your request in this time. I may add `syslog` to OPTIONAL with `... -
- https://github.com/ruby/ruby/commit/3a9e48b9a4860022f43d8101c0f3249299437886 this seems better but I still question the rationale.
I don't see the point in giving `fiddle` special treatment with `OPTIONAL`. What problem is this solvin... -
- RHEL8 and Amazon Linux 2 are failed with `Cannot allocate memory - fork(2)` from Sep 26th.
* http://rubyci.s3.amazonaws.com/rhel8/ruby-master/log/20240926T093004Z.fail.html.gz
* http://rubyci.s3.amazonaws.com/amazon2/ruby-master/log/... -
- Also, when `RUBY_DEBUG` is enabled, objects allocated in shared-gc
fail at `rb_ractor_confirm_belonging`, so assert it always. -
-
-
08:43 AM Revision 239c1c62 (git): LLVM 20 begun
- see also https://github.com/llvm/llvm-project/commit/10c6d6349e51bb245b9deec4aafca9885971135b
-
- I enabled `-O3` build and those tests. But it failed with flaky status.
https://github.com/ruby/ruby/actions/runs/11098648054/job/30831665071#step:6:2439
```
[251/251] 53150=test_range
worker 53144=test_euc_jp does not respon... -
- 07:02 AM Revision f14d5210 (git): * 2024-09-30 [ci skip]
-
- https://github.com/ruby/actions/actions/runs/11095032727/job/30823174026#step:3:349
-
- `make-snapshot` is broken now with the following failure.
```
Command Line Error:
Unknown switch:
-l
creating zip archive... /home/runner/work/actions/actions/pkg/snapshot-ruby_3_3.zip 0.003 failed
```
I opened PRs to stable ... -
- The test case: https://github.com/ruby/ruby/pull/11715/files
-
-
-
- https://github.com/rubygems/rubygems/commit/4c79ab9b2e
-
- https://github.com/rubygems/rubygems/commit/26f6600197
-
- Closes https://github.com/rubygems/rubygems/pull/8068
This issue only occurs if the underlying stub is a gem stub:
https://github.com/Earlopain/rubygems/blob/f56098d8a193dcb94584d721e82b8cff397e5265/bundler/lib/bundler/stub_specificatio... -
- https://github.com/rubygems/rubygems/commit/6a76fedfd0
-
- https://github.com/rubygems/rubygems/commit/b2adcc0173
-
- Since `Gem::Uninstaller` no longer changes paths either.
https://github.com/rubygems/rubygems/commit/427059d45f -
- This could happen when a regular gem shadows a default gem.
https://github.com/rubygems/rubygems/commit/9ef70dd1f7 -
- https://github.com/rubygems/rubygems/commit/e6e3db821f
-
- I think there is no task in this ticket. Thank you @zverok
-
- We can't support Solaris anymore.
-
-
- https://github.com/ruby/actions/actions/runs/11095032727/job/30823174026#step:3:349
-
-
- I disabled this test at https://github.com/ruby/ruby/commit/a896c4cc532b9192732af02ac5cb84d3b5e7f82d
-
- This is fixed by https://github.com/ruby/ruby/pull/11719
-
- Just show error messages then ignore the invalid library.
-
-
-
-
09/29/2024
-
- Since the prism parser was enabled by default, loading scripts with nonascii characters somewhere in the script path is no longer working.
It only works when the codepage was switched to 65001 (UTF-8).
This patch doesn't change the enco... -
- Hello,
This is my first contribution here. I have seen previous discussions around introducing a pipe operator, but it seems the community didn't reach a consensus. I would like to revisit this idea with a simpler approach, more of a ... -
- Failures due to the external setting is not a bug of ruby itself.
-
-
- It is checked in ubuntu.yml.
-
- As `ENABLE_PATH_CHECK` is defaulted to 1 on other than DOSISH and
Cygwin, setting this macro to 1 on Ubuntu changes nothing from the
default. As for `ENABLE_PATH_CHECK=0` tests, we have real CI
platforms already. -
02:27 PM Feature #20769: Add `Hash#transform_value`
- Thank you for sharing that code sample. It demonstrates an interesting way to use `Hash#merge` with a block argument.
When the key argument is absent from the Hash, a call to `Hash#transform_value` would be a no-operation. I apologize... -
- ```ruby
hash.merge(image: nil) {|_, url| download(url)}
hash.merge!(image: nil) {|_, url| download(url)}
``` -
- Join with a space in `MakeMakefile#libpathflag` instead.
- 01:24 PM Revision 9138b388 (git): Update bundled gems list as of 2024-09-29
-
-
-
-
-
-
- The values of `@@map` are `Symbol`s and `@value` should be an
`Integer` since unpacked as unsigned long, so this comparison should
be false always. Probably comparison with `Symbol` was intended. -
-
-
-
-
-
-
-
-
-
09/28/2024
-
- Add `Hash#transform_value` as a specialized, key-specific version of [Hash#transform_values](https://docs.ruby-lang.org/en/3.3/Hash.html#method-i-transform_values).
```ruby
hash = { image: "https://example.com/image.jpg" }
mutated_h... - 09:12 PM Revision 87212a54 (git): [rubygems/rubygems] Improve Gem::SpecFetcher tests.
- https://github.com/rubygems/rubygems/commit/6e0456583b
- 09:12 PM Revision 5c18b63d (git): [rubygems/rubygems] [tests] Don't expect suggestions that aren't actually helpful.
- https://github.com/rubygems/rubygems/commit/e7d6b92e31
- 09:12 PM Revision 47a3482a (git): [rubygems/rubygems] Remove code that makes suggest_gems_from_name give worse results.
- https://github.com/rubygems/rubygems/commit/09ec67ffdf
-
- Add `Hash#delete_at` to delete values from a list keyed by its arguments.
The interface and return values draw inspiration from [Hash#values_at](https://docs.ruby-lang.org/en/3.3/Hash.html#method-i-values_at) and [Array#delete_at](ht... -
-
-
07:05 AM Bug #20767 (Closed): VM_ASSERT fails on clear_method_entry_by_id_in_class() under a specific situation
- VM_ASSERT in `clear_method_entry_by_id_in_class()` (vm_method.c) fails when:
* Kernel#require is refined
* Kernel#require is replaced by `alias_method` and `define_method`
* User code calls `require`
* The aliased method entry is u... -
- These are syntax error with --parser=parse.y. I think it should be syntax ok.
```ruby
def (1...).f; end
def (tap{1...}).f; end
```
ruby-3.0: Syntax OK (checked with 3.0.6)
ruby-3.1: Syntax Error (checked with 3.1.4)
ruby --parse... -
- ~~~
# ruby --parser=prism -e "a=>*,"
-e: [BUG] Unexpected node type in pattern matching expression: PM_IMPLICIT_REST_NODE
# ruby --parser=parse.y -e "a=>*,"
-e:1: syntax error, unexpected end-of-input
~~~ -
- These codes are all syntax error
~~~ruby
->...{}
->(...){}
->(a,...){}
~~~
But these are allowed in --parser=parse.y. It should be syntax error
~~~ruby
->a,...{}
->(a=1,...){}
~~~
~~~
# ruby --parser=parse.y -e "p ->a,...{}... -
- >By the way, I share @Earlopain's questions about the additional patch
Ah, thanks. It's simple bug. I'll fix at next week.