suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
racket/collects/racket/contract/private/guts.rkt
View File

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

4
racket/collects/racket/contract/private/prop.rkt
View File

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