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
P4C currently uses boost::multiprecision to calculate big integers. However, p4-constraints uses GMP. Is there a particular reason why GMP was chosen?
P4C used to have it, but ultimately went with boost because of license concerns. GMP uses GPL, although I do believe it is the variant with linking exceptions.
Reason I am asking is because once we integrate p4-constraints into P4C it would be nice to pick one of these big integer libraries.
The text was updated successfully, but these errors were encountered:
We felt that GMP was the lighter/more stable dependency of the two, since Boost provides much more than just big integers. That said, this decision wasn't super well researched or anything, using Boost instead may be fine.
P4C currently uses boost::multiprecision to calculate big integers. However, p4-constraints uses GMP. Is there a particular reason why GMP was chosen?
P4C used to have it, but ultimately went with boost because of license concerns. GMP uses GPL, although I do believe it is the variant with linking exceptions.
Reason I am asking is because once we integrate p4-constraints into P4C it would be nice to pick one of these big integer libraries.
The text was updated successfully, but these errors were encountered: