-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
Reworked the book/tutorial #1379
Conversation
@bilelmoussaoui do you maybe have some input for this PR as well? |
I will review this tomorrow morning |
Rebased |
Do you have some feedback Bilal? |
Sorry for taking too long, I have been busy with finishing up the release. I will get back to this as soon as possible |
Yes, of course. I didn't want to be impolite. |
Rebased |
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.
A first round of reviews, haven't had the time/energy to go through all of it yet but will get back to it in the upcoming days, thanks a lot!
|
||
- `normal`: generates another crate for a layer on top of these unsafe (sys) bindings which makes them safe for use in general Rust. | ||
|
||
- `not_bound`: allows you to see the detected types/methods that will not be generated for whatever reasons. |
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.
The not_bound
mode was dropped from the docs, it should be still mentioned as it is pretty useful when you are working on a new library bindings or if the library changes a lot.
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.
It is mentioned in lines 15 & 16 in the same file. Do you want me to rephrase it?
I made changes to address all suggestions. For a few, I need some feedback to fix it. |
@bilelmoussaoui, did you get a chance to review the rest? |
I will have a look this weekend |
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 had a quick look for spelling, not for content.
Not specific to this PR, but I would recommend adding a newline after each sentence.
It doesn't change the output, but makes diffs much more readable in my opinion.
Rebased on the latest master |
Thank you @Hofer-Julian for the suggestions. I have applied all of them. There are currently no other pending suggestions that I am aware of. |
Co-authored-by: Bilal Elmoussaoui <[email protected]> Co-authored-by: Bilal Elmoussaoui <[email protected]> Co-authored-by: Bilal Elmoussaoui <[email protected]> Co-authored-by: Bilal Elmoussaoui <[email protected]> Co-authored-by: Bilal Elmoussaoui <[email protected]> Co-authored-by: Bilal Elmoussaoui <[email protected]> Co-authored-by: Bilal Elmoussaoui <[email protected]> Co-authored-by: Bilal Elmoussaoui <[email protected]>
Thank you for merging it :) |
Sorry for taking so long to review it |
No problem. I understand that it was a lot to read and go through and probably not of the highest priority |
A while ago I created a draft PR ( #1354) to improve the book. A good number of commits were done since then. I am not that familiar with git and I think now the PR is ready, so I created this PR.
A few months have passed and I didn't find the time to add the missing information to explain the whole process of how to create the bindings for pango. The overhaul contains all the information of the current version and adds some to it. I believe this version can already be merged and is already an improvement.
To recap, the improvements include:
A native speaker should probably proofread it.