Incorrect boxing allocation warning

[ScrubN]

In cases where an interpolated string containing a value type is provided as an argument to a method expecting an object, the value type is incorrectly flagged as a boxing allocation.

This can be verified by checking the lowered code (in this case low-level C#), confirming the value type is indeed not boxed by the object cast.

[controlflow]

Thanks for reporting! This needs fix in ReSharper, interpolated string gets incorrectly classified when being converted to System.Object type. I'll fix this soon and will add more tests to cover this case in the plugin.