More useful regexp variables
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 833
- Forks
- 99
- Avg merge
- 9h 30m
- Merged PRs (30d)
- 12
Description
"foo 123 bar".gsub(/\w+/) do
$&.upcase #=> [error] undefined method: nil#upcase
end
It would be great if $&, $1, etc. respects the context.
BTW, Steep seems to handle such variables as always Strings. It is not correct but maybe more useful.
Contributor guide
No contributing guide indexed for this repository
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
Start with the provided gsub example and reproduce how TypeProf types $&, $1, and related regexp variables inside the block. Trace the regexp-match context and determine the expected types for these variables, including the desired behavior for the shown upcase call. Done means the example no longer reports $& as nil while the variable types remain context-aware.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100