> That's only a guess at what `Not` is supposed to do, though. If you need > to make a decision without first forcing the promise, you'll need to use > different types.
I'm playing around with describing circuits using Racket and using TR to type check my ports. Unfortunately I do have to make a decision before forcing the promise, just because in my current design I use nested letrec forms and can't guarantee that the promise is ready. `Not` is just a simple example of something that has a different behavior depending if the input is a single wire or a bundle of wires, but the input could also be a promise that forces to either a wire or a bundle. Ususally when I get myself into a corner and there's not an easy way out, I need to rethink my approach (or goals). Thanks for your suggestions. -Luke
____________________ Racket Users list: http://lists.racket-lang.org/users
