It's buggy. On 32-bit systems (such as WASM?) i64::MAX will overflow.
It's undocumented, so I don't believe it's used outside of this crate. If it is used outside of this crate, I'll edit the PR to use isize instead of i64 to fix the bug, and add documentation.
This PR removes
HIGH_COST
for a few reasons:i64::MAX
will overflow.isize
instead ofi64
to fix the bug, and add documentation.