On Tue, Aug 30, 2016 at 8:18 PM, Kiwamu Okabe <[email protected]> wrote: > By the way, the "aPtr1 style" code is more large than "at-view style" code: > > $ wc -l mutual_struct{2,3}/main.dats > 44 mutual_struct2/main.dats > 53 mutual_struct3/main.dats
Ah, "at-view style" code grows more large, if support `opt`. I think I agree your "aPtr1 style" code has good balance. By the way, I have another question. If we support ATS's record such like no-mutual but including pointer, we should also choose same method as supporting struct? Best regards, -- Kiwamu Okabe at METASEPI DESIGN -- You received this message because you are subscribed to the Google Groups "ats-lang-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/ats-lang-users. To view this discussion on the web visit https://groups.google.com/d/msgid/ats-lang-users/CAEvX6dmjFxB1JLiA0vhzrmXiSV5a8YtpBHApCrha56Lo6No6%2BA%40mail.gmail.com.
