Re: [racket-users] Pitfall for contracts with serializable structs

[ tl;dr See the newly added struct-guard/c ] I agree this is a problem (and a pernicious one!). Thinking about it from the contract system design point of view, the way serializable struct work this looks a lot like the situation where the module author has (separately) exported the constructor w

[racket-users] Pitfall for contracts with serializable structs

I was (relatively) recently bitten by an issue with putting contracts on serializable structs. What's worse, once I figured out what was going on, I realized that I'd run into this very issue before and even discussed it on this list