Update {Method,UnboundMethod,Proc}#source_location signatures to match Ruby 4.1

[eregon]

• Needed for Reapply "[Feature #6012] Extend source_location for end position ruby#15580

[eregon]

This doesn't work in CRuby CI, see https://github.com/ruby/ruby/actions/runs/20595820151/job/59150151742?pr=15580
What should I do then?
Exclude the tests with tool/rbs_skip_tests?
Or rebase this on top of 3.10.0 since the failures might be caused by other changes on master?

[eregon]

From #1203 (comment)

Generally, the core library RBS definition targets the latest release of Ruby.

So if that's still the case, and it seems to be according to docs then I should use tool/rbs_skip_tests I guess.
Those docs should mention that then.

BTW these errors mention

💡You can skip this test test_each_paragraph(RBS::AST::Ruby::CommentBlockTest) by adding the name to /home/runner/work/ruby/ruby/src/tool/rbs_skip_tests

But these errors don't.

I also wonder if it's good to run RBS tests related to the core library in ruby/ruby CI since we know at least some of them will fail, so not sure there is much value.
This repo seems to test against ruby-head, not sure how that works though then given those differences.

[soutaro]

@eregon Hi! Sorry for the late reply.

We’ve discussed the idea of moving the RBS definitions for core/stdlib classes into the ruby/ruby repository, so that committers can fix method types and their tests together with the Ruby implementation. I’m confident we’ll do this, though probably not within the next few weeks. (Maybe within months...)

For the current core/stdlib test failures, please use rbs_skip_tests in ruby/ruby. I’ll update the documentation as you suggested.

The bundled version of RBS is 3.10, but the master branch targets RBS 4.0 (unreleased), which is causing the CommentBlockTest failure. (Though I’m still not sure why.)

[eregon]

We’ve discussed the idea of moving the RBS definitions for core/stdlib classes into the ruby/ruby repository, so that committers can fix method types and their tests together with the Ruby implementation. I’m confident we’ll do this, though probably not within the next few weeks. (Maybe within months...)

That would be great!

For the current core/stdlib test failures, please use rbs_skip_tests in ruby/ruby.

Right, it's what I did.

I’ll update the documentation as you suggested.

Thanks!

[eregon]

This repo seems to test against ruby-head, not sure how that works though then given those differences.

Any insight on this? At first sight it seems weird that rbs master + ruby master works in ruby/rbs CI but not in ruby/ruby CI. I suppose they run different tests?