-
Notifications
You must be signed in to change notification settings - Fork 80
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
Going through all the documentation and trying to use #15
Conversation
new reference links.
For instance this line here: https://github.com/CGMossa/tabled/blob/25c331008023fecce39736ef4e3ec2d0adbe6631/src/panel.rs#L5-L6 |
Also, I don't really understand the |
Hi @CGMossa,
So yes it certainly a bit outdated doc comment. Good catch 👍 |
Overall I agree that documentation itself deserve to be polished. |
You can basically remove any row/column by |
Great! Thanks for the answer. I've removed these lines. Feel free to add any other suggestions, and merge it when you're happy with it. |
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.
I actually like all your changes 💯
And I wasn't aware that when something is in scope you can refer on it in doc just like [something]
so thanks for the lesson :)
But this feature brings compiler warnings. Wouldn't it be better to follow old fashioned (not actually) approach like this [Table]: ./struct.Table.html
?
warning: unused import: `Table`
--> src/alignment.rs:1:25
|
1 | use crate::{CellOption, Table};
| ^^^^^
|
= note: `#[warn(unused_imports)]` on by default
warning: unused import: `Table`
--> src/disable.rs:1:30
|
1 | use crate::{bounds_to_usize, Table, TableOption};
| ^^^^^
warning: unused import: `papergrid::Grid`
--> src/object.rs:6:5
|
6 | use papergrid::Grid;
| ^^^^^^^^^^^^^^^
warning: unused import: `Disable`
--> src/panel.rs:1:13
|
1 | use crate::{Disable, TableOption};
| ^^^^^^^
warning: 4 warnings emitted
Based on what I've read here: rust-lang/rust#79542, I think we should just do with the |
The same issue showcases a "better" pattern that is also discouraged in the same thread: /// [`HashMap`]
///
/// [`HashMap`]: std::collections::HashMap
pub fn foo() {} |
Thanks for your PR. |
I really, really appreciate this package. And I wanted to go through it and
use the new way to refer to types in rustdoc. A few things have come up, that
would be nice if we could go through: