Special handling for Array#min, max, etc.

Open
#61 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
compilers

Research direction

Start by reading the Array[Elem]#min RBS definition and the type inference path for non-empty tuples. Trace how the example [1, 2, 3].min.to_s(2) is resolved; done means a non-empty tuple's min, max, and related methods are inferred as Elem rather than Elem | nil, so the example no longer reports nil#to_s.

Written by the indexing model from the issue text.

Description

as = [1, 2, 3]
as.min.to_s(2) #=> [error] failed to resolve overload: nil#to_s

Array[Elem]#min returns Elem | nil in RBS definition. It is correct but it would be useful to return Elem when the receiver is a non-empty tuple.

Dominant language
Ruby
Stars
833
Forks
100
PR merge metrics
No merged PRs in 30d

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ruby/typeprof

All issues in ruby/typeprof

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.