So we _can_ do this, but since provides/requires are between modules, and
thus it's the enclosing module that made the contract here, we should blame it for the misuse, not the contract boundary in which the call was made (though further thought should be put towards this). svn: r11687
This commit is contained in:
parent
eb919c78d1
commit
e2c770ab45
|
@ -274,8 +274,7 @@ improve method arity mismatch contract violation error messages?
|
|||
#`(-contract contract-id
|
||||
id
|
||||
pos-module-source
|
||||
(or '#,(syntax-parameter-value #'current-contract-region)
|
||||
(module-source-as-symbol #'name))
|
||||
(module-source-as-symbol #'name)
|
||||
#,(id->contract-src-info #'id))))))])
|
||||
(when key
|
||||
(hash-set! saved-id-table key lifted-id))
|
||||
|
|
Loading…
Reference in New Issue
Block a user