[Reassociate] Guard `add`-like `or` conversion into an `add` with profitability check
This is slightly better compile-time wise, since we avoid potentially-costly knownbits analysis that will ultimately not allow us to actually do anything with said `add`.
Loading
Please sign in to comment