> Easy enough: > So, the code would be wrapped by "contract verification" wrt. the > types.db > > The same could apply to the calling site. With "types-enforces" > instead > of simply compiling a call to my-work-load something like this could > be > expanded: > > (receive (a b c) > (my-work-load > (begin (assert (fixnum? p1)) p1) > (begin (assert (fixnum? p2)) p2)) > (assert (fixnum? a)) > (assert (fixnum? b)) > (assert (fixnum? c)) > (values a b c)) > > Thus I could switch either site into debug mode. When in this mode > I could be sure that successfully invoking a procedure means all > parameters > have been checked.
There already has been some preparation for type-check generation (at procedure entry). I'll look into make that usable. cheers, felix _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
