You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Types that use rstd::boxed::Box are declared to the api without the box wrapper. For example if my type is type BoxedInt = Box<u64> it should be declared to the api as { "BoxedInt": "u64" }.
However developers may reasonably guess that it should be declared as { "BoxedInt": "Box<u64>" } especially considering how Vec<_>s are declared. To lower the friction for new developers, it would be nice to automatically strip the unnecessary Box when it is supplied.
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.
Types that use
rstd::boxed::Box
are declared to the api without the box wrapper. For example if my type istype BoxedInt = Box<u64>
it should be declared to the api as{ "BoxedInt": "u64" }
.However developers may reasonably guess that it should be declared as
{ "BoxedInt": "Box<u64>" }
especially considering howVec<_>
s are declared. To lower the friction for new developers, it would be nice to automatically strip the unnecessary Box when it is supplied.The text was updated successfully, but these errors were encountered: