fix syntax: change pub(super) enum to pub enum #926
Merged
Conversation
This file contains 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
|
Thanks for fixing this, That is weird, I am not able to reproduce this issue, but better to change the syntax here. What Rust version you are using? |
cargo 1.73.0 (9c4383fb5 2023-08-26) |
|
Right, seems like an issue with the Rust level. The minimum will change in master to 1.75 from now on. |
This was referenced May 15, 2024
juhaku
pushed a commit
that referenced
this pull request
Oct 7, 2024
Co-authored-by: cuihao <[email protected]>
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.
When I was using utoipa, I found a syntax error that prevented me from completing the cargo build. pub(super) enum str will cause the function parse_next_literal_str_or_include_str error on L.2913 in this file. As shown in the figure below:
Therefore, the deletion (super) is consistent with the
pub enum Valueon L.2856 in this file.Resolves #908 Resolves #918