[Rust] Allow to supply a default string value - #5562
Open
kistz wants to merge 25 commits into
Open
Conversation
Contributor
Author
|
@gefjon could you take a look at this? :> |
Collaborator
|
Regardless of the order of PR merges, I think the tests in #5618 are the best coverage for this, so I had the bot revert the test changes. Other than that, I'm fine to merge in any order if you want to move this out of draft. |
Contributor
Author
kistz
marked this pull request as ready for review
July 31, 2026 12:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of Changes
Rust modules cannot do it at the moment.
Allow it by taking in a
&'static str.The approach in the macro is safe because we always have a
std::Stringenforeced by theSpacetimeTypeimplementation.API and ABI breaking changes
None. Additive changes
TODO: Update the documentation aswell if approach is good enough.
Expected complexity level and risk
1
Testing