Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Type cases for subtracting 1 from Int>1 producing PosInt #883

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

AlexKnauth
Copy link
Member

Refines the types of sub1 and (- _ 1) so that if the argument has a positive integer type known greater than 1, the result of subtraction still has a positive integer type.

This is useful in cases where a function recurs on a positive integer and treats 1 as the base case. In the else case, it's known to not be 1, so the sub1 should be known to be positive:

(define-predicate one? One)
(: pick1 (-> Positive-Integer (Listof Any) Any))
(define (pick1 n lst)
  (cond [(one? n) (car lst)]
        [else (pick1 (sub1 n)
                     (cdr lst))]))

@samth
Copy link
Sponsor Member

samth commented Dec 6, 2019

This should be easy to do with refinement types. Do we think it's worth adding more cases to the numeric tower for?

@AlexKnauth
Copy link
Member Author

Okay, I see your point, this slight variation passes using #:with-refinements

#lang typed/racket #:with-refinements
(: pick1 (-> Positive-Integer (Listof Any) Any))
(define (pick1 n lst)
  (cond [(= 1 n) (car lst)]
        [else (pick1 (sub1 n)
                     (cdr lst))]))

However, is there a way to make it typecheck by default, without the user having to add #:with-refinements at the top?

@samth
Copy link
Sponsor Member

samth commented Apr 13, 2020

I'm still skeptical that we should take this route to more precise typechecking of numeric types, rather than using refinements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants