New Issue: BigInteger coercions

17743, "lydia-duncan", "BigInteger coercions", "2021-05-14T18:10:40Z"

Over on Should there exist ** with a bigint as the exponent but the base is an integral? · Issue #17689 · chapel-lang/chapel · GitHub Brad said:

it makes me wish we had int->bigint and uint->bigint coercions so that [cases like exponentiation with an integer base] would just "fall out" rather than requiring explicit overloads
... it seems like it could remove some redundancy in the code base for cases where we're just taking the integral, converting to bigint, and calling the bigint version? And it'd be an issue in which coercions seem very reasonable to carry along the conversation we started after the last release