<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Jun 29, 2016, at 9:05 AM, Stephen Canon <<a href="mailto:scanon@apple.com" class="">scanon@apple.com</a>> wrote:</div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">We’re a little bit off in the weeds here =)</div></div></div></blockquote></div><div class=""><br class=""></div>I was only providing examples of why we might not want to tie `Arithmetic` to, um I think `Syntax.Literal.Integer` is the latest suggestion. I know they aren’t perfect, but they all seem to be not <i class="">too</i> far-fetched (except the HTMLParser).<div class=""><br class=""></div><div class="">If you’re suggesting we start a thread about what it’d take to rework `Arithmetic` to support modeling rings and fields, I am <i class="">totally</i> on-board… :-)</div><div class=""><br class=""></div><div class=""><div class="">- Dave Sweeris</div><div><blockquote type="cite" class=""></blockquote></div></div></body></html>