On 08/24/2016 02:28 PM, Alex Knauth wrote: > That's the short-term solution. A better solution would be for typed racket > to implement a different version of #:opaque that would actually wrap the > values in opaque structs when they flow from untyped-to-typed and unwrap them > when they flow from typed-to-untyped. That way typed racket would know how to > protect the values.
we will be eagerly awaiting such a change to typed racket, as unsafe requires are worrisome. If a lay-programmer could contribute do let me know, though I am not sure I know where to start. -- Matthew Eric Bassett | http://mebassett.info -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
