Summary

define-record-type does not check constructor arguments

Metadata

Description

Pointed out by Zipheir on IRC:

 #;1> (define-record-type <wrong> (wrong value) wrong? (valur wrong-value))
 #;2> (wrong-value (wrong 10)) => #<unspecified>

This should probably be an expansion time error, that value doesn't exist (notice the type in the valur attribute).

Changes and comments

[2019-07-14 22:42:17 UTC] sjamaan changed description

[2019-10-11 18:30:55 UTC] kooda changed status from new to closed

[2019-10-11 18:30:55 UTC] kooda set resolution to fixed

[2019-10-11 18:30:55 UTC] kooda wrote:

Fixed by 721d8a592bb07c91eb093051d922c825b230a9b0