Issue 1966: ref struct challenges

[jonlegendre]

Hi Brad and all,
I am considering addressing 1966.
After cursory investigation I am finding that this will likely require a significant amount of code as the ref struct types, such as span and ReadOnlySpan will not be supported by much of the existing code, which is expecting object parameters; these ref struct types don't support boxing to object. For example, the constructors for AssertActualException require objects for the actual and expected parameters, so these ref struct types are not supported.
Are you expecting significant code for this solution (i.e. creating new methods and classes that can accept these various ref struct type parameters)? Or should I just consider a sort of pseudo-boxing by converting the ref struct entities to string and invoking existing methods?

Thank you,
Jon

[bradwilson]

I have no idea how much code to expect. 😛

[jonlegendre]

Brad et al,
I just submitted a pull request for the changes. This ended up being less impactful than I anticipated due to some nifty support for conversions to other types in the memory extensions classes, and some implicit operators and behaviors.
I realized after completing the code that this was not an accepted help wanted change, so no worries if this is rejected, it was a fun bit of code to play with.

[bradwilson]

This all got merged, so closing this discussion.