<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Oct 26, 2018, at 9:43 PM, Carter Schonwald <<a href="mailto:carter.schonwald@gmail.com" class="">carter.schonwald@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">ORDER of the abstracted constructors matters!</span></div></blockquote></div><br class=""><div class="">That's a very good point. So we don't have a set of sets -- we have a set of lists (where normal constructors -- which have no overlap -- would appear in the lists in every possible permutation).</div><div class=""><br class=""></div><div class="">Again, please don't take my set of lists too seriously from an implementation point of view. We clearly wouldn't implement it this way. But I want to use this abstraction to understand the shape of the problem and what an idealized solution might look like before worrying about implementation and syntax.</div><div class=""><br class=""></div><div class="">Richard</div></body></html>