You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Swift has an... interesting approach to numeric protocols. It's a real helter-skelter mix of some that add operations, make things integer-y, make things floating-point-y, signal access times for collections-y, etc. What it doesn't do is actually define a good hierarchy of the values their numeric structures can represent. I think we can fix that.
The NInt et al machinery can be collapsed and reappropriated for arbitrary precision arithmetic (somehow. GMP, OpenSSL, CommonCrypto?). We can define proper numeric type classes and conformances for swift types and get real numeric constraints going for once.
The text was updated successfully, but these errors were encountered:
Swift has an... interesting approach to numeric protocols. It's a real helter-skelter mix of some that add operations, make things integer-y, make things floating-point-y, signal access times for collections-y, etc. What it doesn't do is actually define a good hierarchy of the values their numeric structures can represent. I think we can fix that.
The NInt et al machinery can be collapsed and reappropriated for arbitrary precision arithmetic (somehow. GMP, OpenSSL, CommonCrypto?). We can define proper numeric type classes and conformances for swift types and get real numeric constraints going for once.
The text was updated successfully, but these errors were encountered: