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.

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 moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Unclear (2 comments)

1 answer

+2
−0

Option 1. The docstring precedes the attributes by convention. Here is an example of the docstring for std::vec::Vec.

However, if using cargo doc to generate documentation, it works just fine if you put it after as well.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

Convention or enforced? (3 comments)

Sign up to answer this question »