Bugfix in Transition class with a stricter type check for boxing required types

[victorr99]

Description

The Transition class performs a check which tells if type A is assignable to type B. This check did not take types into account which require boxing if you want to assign them (value types like int must be boxed in order to be assignable to object).

Similar checks are done at two other places. I haven't touched these two places because I'm not sure if the fix needs to be applied there to. I guess that the FinalTransition is used when the last call in the expression is not an await call? In that case I think the current behavior is already correct (if you want to return an int from a lambda with return type object, the int must be boxed with a Convert call)

1. hyperbee.expressions/src/Hyperbee.Expressions/CompilerServices/Transitions/Transition.cs

   Line 39 in 0eddf5a

   if ( value != null && variable.Type.IsAssignableFrom( value.Type ) )

2. hyperbee.expressions/src/Hyperbee.Expressions/CompilerServices/Transitions/FinalTransition.cs

   Line 35 in 0eddf5a

   if ( variable.Type.IsAssignableFrom( lastExpression.Type ) )

This PR fixes this issue:

• Fixes [BUG]: Incorrect handling of value-type to object assignment when using BlockAsync (missing boxing) #126

Type of Change

• Bug fix
• New feature
• Documentation

Checklist

• I have run the existing tests and they pass
• I have run the existing benchmarks and verified performance has not decreased
• I have added new tests that prove my change is effective or that my feature works
• I have added the necessary documentation (if applicable)

[avarndell]

Looks good

[victorr99]

Thanks for the review. Not sure if we still need to this PR because @bfarmer67 has a fix ready in #133 . As far as I know he's waiting for this issue to be addressed: dadhi/FastExpressionCompiler#495

[bfarmer67]

Addressed in #133