Peter Bex <peter....@xs4all.nl> writes: > As I understand it, strict-types declares variables to never change > their types. So once it's looked at the initial declaration of the > variable, it assigns it a type of null, and then it can never change. > > -strict-types assume variable do not change their type > > The set! would change the type from NULL to LIST (or maybe PAIR), > invalidating that assumption.
Ah, very good, that should explain it. I somehow had it remembered as "assume functions are always called with correctly typed arguments" or something. Should have RTFM :-) Thanks! Moritz _______________________________________________ Chicken-hackers mailing list Chicken-hackers@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-hackers
