<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Found the link for the paper I read about the “ropes” data type. Figured I’d share it around for interested folks.<div class=""><br class=""></div><div class=""><a href="https://www.cs.rit.edu/usr/local/pub/jeh/courses/QUARTERS/FP/Labs/CedarRope/rope-paper.pdf" class="">https://www.cs.rit.edu/usr/local/pub/jeh/courses/QUARTERS/FP/Labs/CedarRope/rope-paper.pdf</a></div><div class=""><br class=""></div><div class="">ALSO! Grab this next one quickly, as it’s free on the ACM’s digital library for a limited time due to them opening up the library during the COVID-19 crisis. It’s a paper describing an experience implementing Ropes using Traits in Pharo. It seems that much more significant per-capita reductions in code duplication were achieved by using Traits in the Ropes implementation than were accomplished in the older experiment (referenced in the paper) which involved reimplementing the collections hierarchy using Traits. Seemed relevant to the conversation, and given the limited window for people without ACM memberships to download it, I had to bring it up:</div><div class=""><br class=""></div><div class=""><a href="https://dl.acm.org/doi/10.1145/1028664.1028771" class="">https://dl.acm.org/doi/10.1145/1028664.1028771</a></div><div class=""><br class=""></div><div class="">—Casey</div></body></html>