ufuk (Ufuk Kayserilioglu)
- Login: ufuk
- Registered on: 05/25/2020
- Last sign in: 02/15/2026
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 5 | 5 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| Ruby | Contributor | 03/03/2025 |
Activity
02/15/2026
-
03:01 PM Ruby Feature #19979: Allow methods to declare that they don't accept a block via `&nil`
- @kddnewton There is already a PR with both parse.y (from @nobu) and Prism changes: https://github.com/ruby/ruby/pull/11065
I'd be happy to rebase, update that branch and merge any other changes you think are important for Prism.
01/14/2026
-
- @Dan0042 If the proposed method isn't going to raise an exception, then how would one disambiguate between a `nil` result because the collection has a single entry which is `nil` and a `nil` result since the collection has (for example) ...
12/23/2025
-
- Please post the C level backtrace as well. Usually that's very helpful.
11/18/2025
-
- Did 3.5-preview1 have the same behaviour? If not, could you bisect between the two releases to find the commit that changed the behaviour?
11/09/2025
-
- From the docs https://docs.ruby-lang.org/en/3.4/Kernel.html#method-i-Integer:
> With base zero, string object may contain leading characters to specify the actual base (radix indicator):
> ...
So, your strings are interpreted as octa...
11/05/2025
-
- retro (Josef Šimánek) wrote in #note-17:
> @mame so why to release 4.0 if not causing major breaking changes?
Quoting [my answer to this](https://bugs.ruby-lang.org/issues/21657#note-3) from above:
> ... that is completely a decisio...
11/02/2025
-
- Isn't this related to this problem with GCC? https://bugs.ruby-lang.org/issues/21655#change-114967
10/30/2025
-
- IMO, ranges should behave the same when `end == Float::INFINITY` and when `end == nil`. They are both practically endless ranges, but nothing normalizes them so that they always behave the same. Maybe `(1..1/0.0)` should be internally tr...
10/29/2025
-
- It seems like the next version of Ruby will be branded as 4.0, but that is completely a decision for @matz to make as he wishes. Ruby version numbers don't follow semantic versioning, so 4.0 doesn't mean that there will be breaking chang...
-
- There is a configuration file to control which labeled PRs make it into the automated release notes and which ones should be excluded. I can help set that up if it will be helpful.