-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📝 Add documentation to packet_falcon_core
#24
base: develop
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are all nitpicks and absolutely not blockers. But what we discussed before is still a problem. I could not get a solid grasp on what the "seed-flavored" traits are really meant for and the external input stuff needs to be explained better.
/// Helper type to write iterators over implementors of the seed-less flavored | ||
/// traits to a minecraft connection. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does it mean to write iterators to a Minecraft connection? As a Bytes
? Each individually?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Iterators over PacketWrite
, meaning iterators over more complex types. U should use the specialized implementations for byte arrays.
#[doc = "Transparent wrapper around an "] | ||
#[doc = stringify!($base)] | ||
#[doc = "."] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#[doc = "Transparent wrapper around an "] | |
#[doc = stringify!($base)] | |
#[doc = "."] | |
#[doc = concat!("Transparent wrapper around an ", stringify!($base), "."] |
This might be more readable
@@ -36,13 +42,10 @@ macro_rules! impl_var_int { | |||
} | |||
|
|||
impl $var { | |||
/// Return the stored value. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/// Return the stored value. | |
/// Return the inner value. |
Sounds more rusty
Apart from the derive macros, all items should be documented. Since this is the crate that does not depend on any other falcon crate, this should be understandable on its own.
Is that the case, is this clear and sufficient documentation?