move late-neg projection warnings to the info level in the logger

because right now they are too noisy to be useful to anyone other
than contract system maintainers. Once the problems inside the contract
library itself is fixed, consider moving these back to warning
This commit is contained in:
Robby Findler 2016-03-30 09:28:36 -05:00
parent bcacb34110
commit bfd2404328
2 changed files with 4 additions and 4 deletions

View File

@ -686,7 +686,7 @@
(cond (cond
[(contract-struct-late-neg-projection ctc) => values] [(contract-struct-late-neg-projection ctc) => values]
[else [else
(log-racket/contract-warning "no late-neg-projection for ~s" ctc) (log-racket/contract-info "no late-neg-projection for ~s" ctc)
(cond (cond
[(contract-struct-projection ctc) [(contract-struct-projection ctc)
=> =>
@ -723,7 +723,7 @@
(define warn-about-val-first? (make-parameter #t)) (define warn-about-val-first? (make-parameter #t))
(define (maybe-warn-about-val-first ctc) (define (maybe-warn-about-val-first ctc)
(when (warn-about-val-first?) (when (warn-about-val-first?)
(log-racket/contract-warning (log-racket/contract-info
"building val-first-projection of contract ~s for~a" "building val-first-projection of contract ~s for~a"
ctc ctc
(build-context)))) (build-context))))

View File

@ -291,7 +291,7 @@
(unless get-late-neg-projection (unless get-late-neg-projection
(unless first-order? (unless first-order?
(log-racket/contract-warning (log-racket/contract-info
"no late-neg-projection passed to ~s~a" "no late-neg-projection passed to ~s~a"
proc-name proc-name
(build-context)))) (build-context))))
@ -464,7 +464,7 @@
(unless late-neg-projection (unless late-neg-projection
(unless first-order? (unless first-order?
(log-racket/contract-warning (log-racket/contract-info
"no late-neg-projection passed to ~s~a" "no late-neg-projection passed to ~s~a"
proc-name proc-name
(build-context)))) (build-context))))