argument types of def foo(...)
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2.2k
- Forks
- 256
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 37
Description
Currently, argument types of def foo(...) is (*untyped), but it will be changed to (*untyped, **untyped **) if ruby/ruby#6818 is merged.
The current behavior depends on the implementation details of ..., which uses ruby2_keywords internally, and I believe (*untyped, **untyped) is right.
@soutaro What do you think?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no file or test. Start by locating the handling of def foo(...) and inspect how its argument types are represented, then compare the current (*untyped) result with the expected (*untyped, **untyped) behavior after ruby/ruby#6818. Done means the signature reflects the intended argument types and has regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100