AFK, but it looks like the contract and function on your define/contract are swapped. Maybe the contract check on the one-arg call sets the parameter and then hilarity ensues?
Eric On Mon, Mar 23, 2020, 12:36 PM David Storrs <david.sto...@gmail.com> wrote: > (define/contract (foo x) > (-> boolean? any) > 'ok) > > (foo #t) > 'ok > (foo 7) > ; foo: contract violation > ; expected: boolean? > ; given: 7 > ; in: the 1st argument of > ; (-> boolean? any) > ; contract from: (function foo) > ; blaming: top-level > ; (assuming the contract is correct) > ; at: readline-input:4.18 > ; [,bt for context] > > Yup, all good. > > > (define/contract foo (make-parameter #f) boolean?) > (foo #t) > (foo) > #t > (foo 7) > #f > > > This isn't what I expected. What am I missing? > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/racket-users/CAE8gKocV-TC1U6g5sq7C%2BZAjSVqDc%2B4yZWobr245qx4fZ9%2Bi3w%40mail.gmail.com > . > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/CAORuSUyw8_sBLzo5B4cx2PursiVzmmM3rBe3USCNn-cPip_ytA%40mail.gmail.com.
