Hi Hongwei, On Wed, Aug 31, 2016 at 3:35 AM, gmhwxi <[email protected]> wrote: > What kind of records do you have in mind?
Sorry for my poor explanation. I wrote following code using ATS record and "at-view style": https://github.com/jats-ug/practice-ats/blob/6f663912d6118899861889f4ef3b835d3ceb5774/mutual_record/main.dats Above code has following unsafe points: A. Create at-view from nothing. https://github.com/jats-ug/practice-ats/blob/6f663912d6118899861889f4ef3b835d3ceb5774/mutual_record/main.dats#L11 B. Assign raw pointer. https://github.com/jats-ug/practice-ats/blob/6f663912d6118899861889f4ef3b835d3ceb5774/mutual_record/main.dats#L25 I think these unsafe things is coming from that ATS record can't maintain at-view in. My motivation is re-writing C language code using ATS language, and getting more safe code. I'll rewrite the C code little by little. At first stage, the ATS code includes some structs from C code. At second state, should I re-write the struct as ATS record? If re-write, I'll get more safe design in ATS code? Or which choose struct/record is not important thing? 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/CAEvX6dkt4HrDajCEg%3DTgGGOC9UQCyTALXAdVaQXDb6QDvFTXGQ%40mail.gmail.com.
