On 2015-12-26 15:52:38 -0800, JCG wrote: > 3) The end-product appears to be a 50%-performance hybrid due to boundary > contracts, but ameliorated runtime-wise by utilizing the > typed/racket/no-check language after it's all working in type checked mode.
If you're using Racket v6.3, another way to get around this is to use the `typed/racket/unsafe` library which allows you to selectively disable some contracts: http://docs.racket-lang.org/ts-reference/Unsafe_Typed_Racket_operations.html That way at least your types won't bitrot as much. Note that as the name indicates, this is potentially less safe than untyped Racket if the TR optimizer is on. (you could also write a wrapper macro that globally enables/disables the use of the unsafe imports & exports) Cheers, Asumu -- 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.
