The technique for addressing integer overflow in a general setting seems too costly. ATS is already very complex at this point.
The mismatch between the statics and the dynamics is explicitly mentioned. For instance, it is mentioned in the last paragraph of the following article: http://ats-lang.sourceforge.net/DOCUMENT/INT2PROGINATS/HTML/HTMLTOC/x2403.html I want re-emphasize that this mismatch is primarily for the purpose of making ATS more accessible. One can and probably should build his or her own arithmetic API in ATS when using ATS for critical low-level programming. It is even better if one is willing to share as well. On Thursday, January 4, 2018 at 1:09:23 PM UTC-5, cmp xchg wrote: > > > hmm. but why didn't you choose the technique presented in your example > for implementing at least array access in the main library? it seems to me > that the current situation is even worse than in plain c. at least the > current > design decisions should be mentioned in the tutorial/introduction > sections? > -- 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 ats-lang-users+unsubscr...@googlegroups.com. To post to this group, send email to ats-lang-users@googlegroups.com. 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/bcb8969a-29a8-4fa4-b196-1180de54ade5%40googlegroups.com.
