Uh oh!
There was an error while loading. Please reload this page.
box_value constructor: Replace param::hstring with hstring - #1530
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Charles Milette (sylveon)
commented
Mar 20, 2026
Ryan Shepherd (@DefaultRyan) This PR is a good one - box_value will always do a copy of the hstring so we might as well skip the |
Ryan Shepherd (DefaultRyan)
commented
Mar 21, 2026
This breaks boxing of string-like types such as I think we can still do this with a little more finesse. One idea of the top of my head is to have an exact |
justanotheranonymoususer
commented
Mar 21, 2026
I tried to fix, can you run tests? |
Ryan Shepherd (DefaultRyan)
commented
Mar 23, 2026
Did you know you can run the tests locally? That break would have been caught there and saved you some time. :) |
justanotheranonymoususer
commented
Mar 23, 2026
I was filling lucky. Should pass now, and I even added tests. |
justanotheranonymoususer
commented
Mar 30, 2026
Ryan Shepherd (@DefaultRyan) it's green now, are we good? |
justanotheranonymoususer
commented
Apr 1, 2026
thx for approving, can you also merge? |
Partial fix for #1527.
Other places remain unfixed, example:
unbox_value_or(boxed, ReturnsStringView());Or any other
param::hstringusage.