ruby.git/lib/prism/polyfill, branch v4.0.4 The Ruby Programming Language [ruby/prism] Use `method_defined?` instead of `instance_methods.include?` 2025-11-14T13:47:49+00:00 Nobuyoshi Nakada nobu@ruby-lang.org 2025-11-14T01:51:20+00:00 0e604623d855934c1f10b293b698f223b79c5c07 While the latter creates an intermediate array of all method names including all ancestors, the former just traverse the inheritance chain and can stop if found once. https://github.com/ruby/prism/commit/6da384dd0e 
While the latter creates an intermediate array of all method names
including all ancestors, the former just traverse the inheritance
chain and can stop if found once.

https://github.com/ruby/prism/commit/6da384dd0e
[ruby/prism] Fix warn polyfill when no uplevel is provided 2025-09-15T11:03:12+00:00 Earlopain 14981592+Earlopain@users.noreply.github.com 2025-09-15T06:39:30+00:00 9299cf31b1607859daf89772b777f19f426bed80 An unspecified uplevel is not the same as an uplevel of 1: ``` $ irb irb(main):001> warn("foo") foo => nil irb(main):002> warn("foo", uplevel: 1) /home/user/.rbenv/versions/2.7.8/lib/ruby/gems/2.7.0/gems/irb-1.14.0/lib/irb/workspace.rb:121: warning: foo => nil ``` https://github.com/ruby/prism/commit/dcedd14357 
An unspecified uplevel is not the same as an uplevel of 1:

```
$ irb
irb(main):001> warn("foo")
foo
=> nil
irb(main):002> warn("foo", uplevel: 1)
/home/user/.rbenv/versions/2.7.8/lib/ruby/gems/2.7.0/gems/irb-1.14.0/lib/irb/workspace.rb:121: warning: foo
=> nil
```

https://github.com/ruby/prism/commit/dcedd14357
[ruby/prism] Fix parser translator during string escaping with invalid utf-8 2025-06-11T18:07:43+00:00 Earlopain 14981592+Earlopain@users.noreply.github.com 2025-06-11T13:28:21+00:00 970813d98285b8f59fe5e4d3c815cc044926cb1b Instead, prefer `scan_byte` over `get_byte` since that already returns the byte as an integer, sidestepping conversion issues. Fixes https://github.com/ruby/prism/issues/3582 https://github.com/ruby/prism/commit/7f3008b2b5 
Instead, prefer `scan_byte` over `get_byte` since that already returns the byte as an integer, sidestepping conversion issues.

Fixes https://github.com/ruby/prism/issues/3582

https://github.com/ruby/prism/commit/7f3008b2b5
[ruby/prism] Polyfill Kernel#warn category parameter 2025-03-19T21:03:18+00:00 Kevin Newton kddnewton@gmail.com 2025-03-19T18:54:12+00:00 050ffab82b1a855d6b6edf5fbc6dc8c9311b6556 https://github.com/ruby/prism/commit/d85c72a1b9 
https://github.com/ruby/prism/commit/d85c72a1b9
[ruby/prism] Fix parser translator crash for certain octal escapes 2025-03-18T17:36:53+00:00 Earlopain 14981592+Earlopain@users.noreply.github.com 2025-01-19T12:38:17+00:00 a679597547b23259159dd914959ca36409878199 `Integer#chr` performs some validation that we don't want/need. Octal escapes can go above 255, where it will then raise trying to convert. `append_as_bytes` actually allows to pass a number, so we can just skip that call. Although, on older rubies of course we still need to handle this in the polyfill. I don't really like using `pack` but don't know of another way to do so. For the utf-8 escapes, this is not an issue. Invalid utf-8 in these is simply a syntax error. https://github.com/ruby/prism/commit/161c606b1f 
`Integer#chr` performs some validation that we don't want/need. Octal escapes can go above 255, where it will then raise trying to convert.

`append_as_bytes` actually allows to pass a number, so we can just skip that call.
Although, on older rubies of course we still need to handle this in the polyfill.
I don't really like using `pack` but don't know of another way to do so.

For the utf-8 escapes, this is not an issue. Invalid utf-8 in these is simply a syntax error.

https://github.com/ruby/prism/commit/161c606b1f
[ruby/prism] Fix parser translator when unescaping invalid utf8 2025-03-18T17:36:53+00:00 Earlopain 14981592+Earlopain@users.noreply.github.com 2025-01-12T19:08:28+00:00 705bd6fadbd5a784d2c0fd52138007404de6a5c2 1. The string starts out as binary 2. `ち` is appended, forcing it back into utf-8 3. Some invalid byte sequences are tried to append > incompatible character encodings: UTF-8 and BINARY (ASCII-8BIT) This makes use of my wish to use `append_as_bytes`. Unfortunatly that method is rather new so it needs a fallback https://github.com/ruby/prism/commit/e31e94a775 
1. The string starts out as binary
2. `ち` is appended, forcing it back into utf-8
3. Some invalid byte sequences are tried to append

> incompatible character encodings: UTF-8 and BINARY (ASCII-8BIT)

This makes use of my wish to use `append_as_bytes`. Unfortunatly that method is rather new
so it needs a fallback

https://github.com/ruby/prism/commit/e31e94a775
[ruby/prism] Prism::Location#adjoin 2024-05-03T19:14:03+00:00 Kevin Newton kddnewton@gmail.com 2024-05-03T18:58:40+00:00 d4a6d0c17781821d967063613fab5992231a5158 https://github.com/ruby/prism/commit/a298db68e3 
https://github.com/ruby/prism/commit/a298db68e3
[ruby/prism] Remove need for Natalie patches 2024-04-25T18:00:09+00:00 Kevin Newton kddnewton@gmail.com 2024-04-25T17:00:58+00:00 b6489e9f62dae9e62a4f978e0cb1091ab13c274c https://github.com/ruby/prism/commit/7fc7e13476 
https://github.com/ruby/prism/commit/7fc7e13476
[ruby/prism] Move polyfill to separate file to type-check it independently. 2024-03-06T21:37:53+00:00 Ufuk Kayserilioglu ufuk.kayserilioglu@shopify.com 2024-03-06T19:36:47+00:00 8d191a9f57fa6ff86f63c98e99be68ed86f3052c https://github.com/ruby/prism/commit/2a583b041b 
https://github.com/ruby/prism/commit/2a583b041b