Activity
From 09/25/2024 to 10/01/2024
10/01/2024
-
10:46 PM Feature #20770: A *new* pipe operator proposal
- 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... -
07:43 PM Feature #20770: A *new* pipe operator proposal
- [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... -
07:02 PM Feature #20770: A *new* pipe operator proposal
- @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... -
06:18 PM Feature #20770: A *new* pipe operator proposal
- 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 ...
-
04:13 PM Feature #20770: A *new* pipe operator proposal
- 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... -
05:56 AM Feature #20770: A *new* pipe operator proposal
- 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. -
07:47 PM Revision 5edc3219 (git): [DOC] Tweaks for Array#keep_if
-
-
07:42 PM Revision 467ebbeb (git): [ruby/prism] Disallow dynamic patterns in labels at top level followed by pipes
- https://github.com/ruby/prism/commit/ccc746f918
-
07:36 PM Feature #20775 (Closed): Gemify win32-registry, win32-sspi and win32-resolv
- 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. -
05:01 PM Revision e320da60 (git): [ruby/reline] Fix Reline crash with invalid encoding history
- (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
-
12:48 PM Revision 3932d8a8 (git): Replace heap_eden_total_slots with objspace_available_slots
-
12:06 PM Bug #20764 (Closed): Forwarding parameter `...` is wrongly allowed in lambda
- 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... -
-
09:41 AM Revision 3ebc85e2 (git): Define RactorLocalSingleton on .mspec.constants
-
-
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... -
04:27 AM Feature #20770: A *new* pipe operator proposal
- 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. -
11:32 AM Revision 5ed67f48 (git): [ruby/rdoc] Only let browser search through source code until it's
- 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
-
-
-
05:09 AM Revision 3a273c47 (git): [rubygems/rubygems] Fix error when changing a path source to a git source if frozen mode
- 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.
09/27/2024
-
-
-
- Thanks @tompng — https://github.com/ruby/ruby/pull/11714 should fix this.
-
- `<compiled>: [BUG] Stack consistency error (sp: 7, bp: 6)` running these codes. No error with --parser=parse.y
~~~sh
ruby -e "1r..; nil"
ruby -e "a=1; a..; nil"
ruby -e "rand..; nil"
~~~
~~~
# ruby -e "1r..; nil"
-e:1: [BUG] ... -
- Fixes [Bug #20763]
-
-
- https://github.com/rubygems/rubygems/commit/2fe0f452a2
-
- I meant that I think in Ruby 3.4 (prior to my patch), the warning would also apply to non Bundler contexts that lead to a `LoadError`, where it would inform that `csv` may not always be present and may need an explicit install from RubyG...
-
- deivid (David Rodríguez) wrote in #note-14:
> I think this would affect both Bundler and non Bundler usages. Currently the warnings recommends to install the gem from RubyGems in non Bundler context, that will also be lost in Ruby 3.4 f... -
- I see that https://github.com/ruby/ruby/pull/11550 was merged which is great but I'm confused about https://github.com/ruby/ruby/commit/ff3f61556fb62d12d57d017f4c54f1a8fd5208be because it basically reverts that PR. If a dependency is opt...
-
- I also really like @ioquatix 's suggestion in https://bugs.ruby-lang.org/issues/6012#note-13 and it is a lot more flexible and more efficient too (since computing e.g. column information if unused is not cheap).
For instance `method.sour... -
- It seems good to revisit this, the workarounds are pretty messy and CRuby-specific, e.g. https://github.com/rails/rails/pull/53055/files
I think @mame 's suggestion in https://bugs.ruby-lang.org/issues/6012#note-12 is fine although I ... -
- * [Feature #6012] Proc#source_location also return the column (eregon)
* How about `{Proc,Method,UnboundMethod}.source_location #=> [path, start_line, start_column, start_offset, end_line, end_column, end_offset]` ?
* How about `{Pro... -
- Thanks for the links, yes, that seems a perfect use case for more information in `#source_location`, going through `RubyVM` APIs for that feels overly complicated for something so simple.
I found https://bugs.ruby-lang.org/issues/6012... -
- Eregon (Benoit Daloze) wrote in #note-7:
> @Earlopain Is there a reason you need this and cannot just use e.g. `Prism.parse("proc {1 + 2}")`?
> ...
This question specifically was about usage that Rails recently adopted for printing the s... -
- In general the entire `RubyVM::AbstractSyntaxTree` module should be considered deprecated (and maybe even removed), given it relies on parse.y internals and that matz said that the Prism API is the official Ruby API for parsing Ruby code...
-
- @Earlopain Is there a reason you need this and cannot just use e.g. `Prism.parse("proc {1 + 2}")`?
A cleaner and portable way to achieve this functionality from a Proc/Method would be if there is a way to retrieve their precise source l... -
-
- These days, I believe there is no value to make `RubyVM::AbstractSyntaxTree` stable.
The official Ruby API to parse Ruby code is the Prism API (regardless of which parser is used internally), as matz said. -
- Since #11698, `parser_str_new` makes `rb_parser_string_t` and `VALUE`
but discards the former, and then `STR_NEW3` makes the same thing
again. -
-
01:58 PM Revision 098649bc (git): [ruby/rdoc] Add home page link to output message
- (https://github.com/ruby/rdoc/pull/1165)
The link is clickable in the terminal and opens the home page in the browser
https://github.com/ruby/rdoc/commit/b7d580afab -
10:34 AM Revision 7f83bd37 (git): Reduce `is_ascii_string` function dependency for parser
- Changed to use `rb_parser_is_ascii_string` function instead of `is_ascii_string` function
-
-
-
-
-
- https://github.com/ruby/ruby/actions/runs/11063957302/job/30741993035#step:8:1816
----
```
/github/workspace/src/basictest/test.rb:2357: [BUG] cannot create a new page after major GC
ruby 3.4.0dev (2024-09-27T03:22:52Z pull/112... -
-
-
-
- reduced parallelism from some 50-ish to 10-ish so that other jobs
can run. -
-
- https://github.com/ruby/ruby/commits/master/.github/workflows/mingw.yml is available today.
-
04:31 AM Revision d7e5133d (git): [ruby/benchmark] Add example for Benchmark.realtime
- https://github.com/ruby/benchmark/commit/0f278be6c1
-
- https://github.com/ruby/benchmark/commit/388236685c
-
-
-
09/26/2024
-
- Yeah, I think it would make sense to update those docs to indicate that it only works when the instruction sequences were compiled with the old compiler.
-
- This is great info, thank you! I'm aware about the non-guarantees for `RubyVM`, just something to live with. `AbstractSyntaxTree.of` already had the same "problem".
Regardless, should `AbstractSyntaxTree.of` documentation be updated i... -
- Note that all the APIs under RubyVM are subject to change, so you're effectively calling internal APIs here. Just so you know going forward.
-
- For a proc you can mirror what `RubyVM::AbstractSyntaxTree.of` is doing under the hood using `RubyVM::InstructionSequence`, as in:
```ruby
my_proc = -> { 1 }
iseq = RubyVM::InstructionSequence.of(my_proc)
node_id = iseq.to_a[4][:... -
- kddnewton (Kevin Newton) wrote in #note-1:
> This is expected behavior. The instruction sequences will have different node ids, so it's not possible to retrieve the RubyVM::AbstractSyntaxTree representation of the AST. If you want to re... -
- This is expected behavior. The instruction sequences will have different node ids, so it's not possible to retrieve the RubyVM::AbstractSyntaxTree representation of the AST. If you want to retrieve the Prism AST, you can do so using `Pri...
-
- https://docs.ruby-lang.org/en/master/RubyVM/AbstractSyntaxTree.html#method-c-of
```rb
RubyVM::AbstractSyntaxTree.of(proc {1 + 2})
# => <internal:ast>:97:in 'RubyVM::AbstractSyntaxTree.of': cannot get AST for ISEQ compiled by prism (... -
- I think this would affect both Bundler and non Bundler usages. Currently the warnings recommends to install the gem from RubyGems in non Bundler context, that will also be lost in Ruby 3.4 for gems like `csv`.
That said, I also tend t... -
- https://github.com/ruby/ruby/pull/11550 seems a good solution to me.
I think it is expected to only get the LoadError for `csv` on 3.4 and not also the warning.
People seeing the LoadError for `csv` would intuitively add `csv` to their ... -
- Maybe I have another solution alltogether:
```rb
begin
gem 'fiddle'
rescue LoadError
# Not available, no require => no warning. Future ruyb versions will hit this.
return
end
# No warning on old versions, will warn for ... -
- @deivid Thanks for sharing. My concern is [here](https://github.com/ruby/ruby/pull/11550#issuecomment-2376573020)
I will consider what's better approach for us with https://github.com/ruby/ruby/pull/11550 and https://github.com/ruby/r... -
- @hsbt found an issue with the simpler approach. It will no longer show information about bundled gem extraction "after the fact". So, it for example keeps warning that `csv` will no longer be part of Ruby starting from Ruby 3.4 when usin...
-
- From duplicate code in `decl_branch_base` and `add_trace_branch_coverage`.
-
- 03:47 PM Revision 9a966a09 (git): [ruby/prism] Fix incorrect reference to AlternationPatternNode as non-void expressions
- https://github.com/ruby/prism/commit/68de31919e
- 03:47 PM Revision a73d80db (git): [ruby/prism] Add fields documentation for AliasMethodNode and AlternationPatternNode
- https://github.com/ruby/prism/commit/6953daebde
-
- https://github.com/ruby/prism/commit/976a3cd0a5
- 01:39 PM Revision e71f8905 (git): Update default gems list at 49057f36efd894663cc879be08ada0 [ci skip]
-
- (https://github.com/ruby/irb/pull/1009)
https://github.com/ruby/irb/commit/04cd2317ef -
-
-
-
- From duplicate code in `rb_CFString_class_initialize_before_fork` and
`rb_str_append_normalized_ospath`. -
-
-
-
-
- Turns out we were not running specs on JRuby, so we introduced a
failure. Seems fine to skip.
https://github.com/rubygems/rubygems/commit/4e2d6affb3 -
- @Matz would you mind to comment on the license? How it should be properly applied? What (SPDX) identifiers should be used?
- 07:34 AM Revision 8cd295ec (git): regparse possible memory leak fix proposal
-
- * [Feature #10459] [PATCH] rfc3339 method for Time
* https://github.com/rails/rails/blob/b88d9af34fbc1c84ce2769ba02584eab2c28ac6e/activesupport/lib/active_support/time_with_zone.rb#L152
* It seems reasonable.
* We introduce that w... -
- https://github.com/ruby/digest/commit/07a5db2f77
-
04:00 AM Bug #13831: error when try to install
- ruby_3_2 commit:2d62c5d3d9a565fe50a3582124e6d4a58d130084 merged revision(s) commit:0d16c36d0ab2afa2ec79b72b229e69c141ebdaba.
-
- [win32/registry] Fallback to UTF-8 for unknown codepages
There are some codepages like cp708 for which no ruby encoding exists:
$ ruby -e "Encoding.find('cp708')"
Traceback (most recent call last):
... - 02:58 AM Revision 7340c1ac (git): Bump actions/checkout in /.github/actions/setup/directories
- Bumps [actions/checkout](https://github.com/actions/checkout) from 4.1.7 to 4.2.0.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](http... -
- Ruby 3.0 is EOL now. We will not backport related changes into `ruby_3_0` branch.
-
09/25/2024
-
- `openssl@1.0` is not related for this build failure.
I could build applied https://bugs.ruby-lang.org/projects/ruby-master/repository/git/revisions/1dfe75b0beb7171b8154ff0856d5149be0207724 on Ruby 3.0.6 with macOS 15.1 beta5. The inst... -
- Following commits will be needed to compile 3.0 with the recent Xcode:
- commit:4113862c0068a8a95d752f5fdf14980f92cd41d7
Do not search for commands with double tool prefixes [Bug #18504]
- commit:17c8bf2c63192036058b03a04edf7a8478e478... -
02:22 PM Bug #20760 (Closed): Ruby 3.0.6 fails to build on macOS 15.0 24A335 arm64
- I support a Rails 6.1 project with Ruby 3.0.6 and am unable to build 3.0.6 on a new mac book pro running macOS 15.0 24A335 arm64.
I've attached the build log the primary failure is related to `maybe_unused` in BigDecimal.
I tried m... -
-
- https://github.com/ruby/prism/commit/dc7164e21c
- 07:43 PM Revision fa7fef27 (git): [ruby/prism] Fix rendering of type overview docs
- https://github.com/ruby/prism/commit/d42bc309cc
-
- https://github.com/ruby/prism/commit/988ac82187
-
-
- https://github.com/ruby/prism/commit/84a9251915
-
- https://github.com/ruby/prism/commit/509ff88e92
-
-
-
-
-
- https://github.com/ruby/prism/commit/b624e09cc6
-
-
04:18 PM Revision 505206b8 (git): YJIT: Cache Context decoding (#11680)
-
- https://github.com/ruby/prism/commit/4daf58f7a0
-
- https://github.com/ruby/prism/commit/9fd0c0901e
-
- https://github.com/ruby/prism/commit/a474017bbe
-
-
- To debug this issue on CI:
http://ci.rvm.jp/logfiles/brlog.trunk_asan.20240922-002945 -
-
- * For Loader.java, do not deserialize the AST if there are errors, so then Java nodes only have non-error types for fields.
https://github.com/ruby/prism/commit/ae78e3c605 -
- The allocated parser string is never freed, which causes a memory leak.
The following code leaks memory:
Ripper.sexp_raw(DATA.read)
__END__
<<~EOF
a
#{1}
a
EOF -
- 02:45 AM Revision 76543a34 (git): Bump github/codeql-action from 3.26.8 to 3.26.9
- Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.26.8 to 3.26.9.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md... -
-
- I merged https://github.com/ruby/ruby/pull/7366 for this.
- 01:43 AM Revision 0d16c36d (git): [win32/registry] Fallback to UTF-8 for unknown codepages
- There are some codepages like cp708 for which no ruby encoding exists:
$ ruby -e "Encoding.find('cp708')"
Traceback (most recent call last):
1: from -e:1:in `<main>'
-e:1:in `find': unknown encoding name - cp708 (Arg... -
-
-