Under Betteridge's Law, I was expecting that a paper so titled [1] would 
conclude that the answer is no. But it does ultimately assert that "In the 
context of current implementation technology, sound gradual typing is dead." 
(With a silver lining that some new research questions have been discovered.)

What is the upshot for those of us whose Racketeering is more in the practical 
rather than research realm? On its face, this paper seems to tell me "don't use 
TR." Is that accurate? Is there a category of practical programs that TR 
remains suitable for? 

I ask this as one of the guinea pigs studied in the paper [2]. I originally 
picked up TR because I was curious whether it would be suitable for a project 
where performance is a key consideration. Instead, TR slowed it down. Though I 
was relieved to learn that my bad programming was not entirely the culprit, now 
I feel bad about helping kill TR.



[1] http://www.ccs.neu.edu/racket/pubs/popl16-tfgnvf.pdf

[2] https://github.com/mbutterick/quad

-- 
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.

Reply via email to