Skip to content

Add doc examples for CString methods. #42470

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

Merged
merged 5 commits into from
Jun 8, 2017

Conversation

frewsxcv
Copy link
Member

@frewsxcv frewsxcv commented Jun 6, 2017

No description provided.

@frewsxcv
Copy link
Member Author

frewsxcv commented Jun 6, 2017

r? @QuietMisdreavus

@arielb1 arielb1 added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Jun 6, 2017
/// assert_eq!(b'f', *ptr as u8);
/// assert_eq!(b'o', *ptr.offset(1) as u8);
/// assert_eq!(b'o', *ptr.offset(2) as u8);
/// assert_eq!(b'\0', *ptr.offset(3) as u8);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm less certain about this one. If people are used to working with raw pointers in Rust this is fine, but i wonder if we can do some other kind of comparison to not have to introduce offset in these docs. I don't anticipate people looking at CString with a solid understanding of Rust pointers. This is frequently an entry point into FFI, so readers may potentially only have a cursory understanding of pointers.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure what else would fit here, let me know if you have any ideas. Or if you'd prefer the offset lines to be removed, I can do that too

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now that I think back on it, this is probably good as-is. I was thinking of something like slice::from_raw_parts and comparing against a byte-string, but that risks losing focus from showing off the actual function being documented. If we come up with something better, we can always send another PR.

@QuietMisdreavus
Copy link
Member

@bors r+ rollup

@bors
Copy link
Collaborator

bors commented Jun 7, 2017

📌 Commit 06f63f5 has been approved by QuietMisdreavus

frewsxcv added a commit to frewsxcv/rust that referenced this pull request Jun 8, 2017
…ples, r=QuietMisdreavus

Add doc examples for `CString` methods.

None
bors added a commit that referenced this pull request Jun 8, 2017
Rollup of 5 pull requests

- Successful merges: #42470, #42490, #42497, #42510, #42512
- Failed merges:
@bors bors merged commit 06f63f5 into rust-lang:master Jun 8, 2017
@frewsxcv frewsxcv deleted the frewsxcv/ffi-cstr-doc-examples branch June 11, 2017 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants