We should be checking the new statement's annotation, if we want type-valid? to
only be defined on types that the programmer can write down.n svn: r307
This commit is contained in:
parent
b20010b51e
commit
b0e056190a
|
@ -372,7 +372,7 @@
|
||||||
(let ([class-entry (get-class-entry tenv class)]
|
(let ([class-entry (get-class-entry tenv class)]
|
||||||
[new-type (if type type ctype)])
|
[new-type (if type type ctype)])
|
||||||
;; the following can only be triggered if the type annontation isn't a type
|
;; the following can only be triggered if the type annontation isn't a type
|
||||||
(if (not (type-valid? tenv new-type))
|
(if (and type (not (type-valid? tenv type)))
|
||||||
(raise-read-error-with-stx
|
(raise-read-error-with-stx
|
||||||
(format "Type annotation ~a on new statement is not a valid type" (printable-type new-type))
|
(format "Type annotation ~a on new statement is not a valid type" (printable-type new-type))
|
||||||
(honu:ast-stx new-type)))
|
(honu:ast-stx new-type)))
|
||||||
|
|
Loading…
Reference in New Issue
Block a user