In cases where the compiler needs to unbox a `long`, `float`, `double` and then
run the exactness check, we were getting a crash. While the selector value is
always boxed, the type (which controls the execution flow) was not, because the
`selectorType` was wrong. This PR addresses this bug.
---
On Tue, 12 Mar 2024 14:06:11 GMT, Aggelos Biboudis
wrote:
> In cases where the compiler needs to unbox a `long`, `float`, `double` and
> then run the exactness check, we were getting a crash. While the selector
> value is always boxed, the type (which controls the execution flow) was not,
> b
On Tue, 12 Mar 2024 14:06:11 GMT, Aggelos Biboudis
wrote:
> In cases where the compiler needs to unbox a `long`, `float`, `double` and
> then run the exactness check, we were getting a crash. While the selector
> value is always boxed, the type (which controls the execution flow) was not,
> b
> In cases where the compiler needs to unbox a `long`, `float`, `double` and
> then run the exactness check, we were getting a crash. While the selector
> value is always boxed, the type (which controls the execution flow) was not,
> because the `selectorType` was wrong. This PR addresses this b
