Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Proper location of docstring on struct with attributes

Post

Proper location of docstring on struct with attributes

+2
−1

When documenting a struct with attributes, where does the docstring go? Before or after the attribute(s)?

Option 1:

/// Does it go here?
#[derive(Deserialize, Debug)]
pub struct Metadata {
    pub version: f32,
    pub contributors: Vec<String>
}

Option 2:

#[derive(Deserialize, Debug)]
/// Does it go here?
pub struct Metadata {
    pub version: f32,
    pub contributors: Vec<String>
}

Option 3 (presumably wrong but adding just in case):

#[derive(Deserialize, Debug)]
pub struct Metadata {
    /// Does it go here? (I assume this would document `version`, 
    /// not the struct)
    pub version: f32,
    pub contributors: Vec<String>
}
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Unclear (2 comments)
Unclear
Karl Knechtel‭ wrote 9 months ago

Is the question supposed to be about correctness, or style? If it's about correctness, did you try each way? Or if you're trying to offer a self-answered canonical, do you have a reason to expect that people would get it wrong? If it's about style, then what criteria do you consider relevant to make the question not completely subjective?

qohelet‭ wrote 9 months ago

It works both ways, I just assumed there is some formal convention perhaps defined somewhere. I couldn’t find it but did see examples of doc strings in the std lib so assume that is the convention but not any kind of standard per se