[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-hackers] testcase -strict-types
From: |
Moritz Heidkamp |
Subject: |
Re: [Chicken-hackers] testcase -strict-types |
Date: |
Sun, 24 Mar 2013 23:18:25 +0100 |
Peter Bex <address@hidden> 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] testcase -strict-types, Jörg F . Wittenberger, 2013/03/24
- Re: [Chicken-hackers] testcase -strict-types, John Cowan, 2013/03/24
- Re: [Chicken-hackers] testcase -strict-types, Moritz Heidkamp, 2013/03/24
- Re: [Chicken-hackers] testcase -strict-types, Peter Bex, 2013/03/25
- Re: [Chicken-hackers] testcase -strict-types, Felix, 2013/03/30
- Re: [Chicken-hackers] testcase -strict-types, Peter Bex, 2013/03/30
- Re: [Chicken-hackers] testcase -strict-types, Felix, 2013/03/30
- Re: [Chicken-hackers] testcase -strict-types, Peter Bex, 2013/03/30
- Re: [Chicken-hackers] testcase -strict-types, John Cowan, 2013/03/30