-
Notifications
You must be signed in to change notification settings - Fork 13k
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
doc: C<->Rust function table #15753
Comments
This is a common request for people coming from C to Rust. Frankly, I also have to dig through the Rust library sources every time I run into these things. |
I've tried a bit: https://gist.github.com/lifthrasiir/e021349c1d0cd55933a5 (incomplete). How do you think about this? |
Given that Rust and C will have different usages, I think a more 'this is how you accomplish x in rust' makes more sense than function<->function |
@lifthrasiir This is absolutely awesome! @steveklabnik In Servo, we do a lot of work that is either porting C code or we have people with a few decades of C experience and all of those functions hardwired into their brains, so this sort of map is super-useful. "this is how you modify strings in Rust" is not nearly as useful in those scenarios as "what did they decide to call |
Yeah, I mean, I'm not saying it's not useful at all. |
I'm pulling a massive triage effort to get us ready for 1.0. As part of this, I'm moving stuff that's wishlist-like to the RFCs repo, as that's where major new things should get discussed/prioritized. This issue has been moved to the RFCs repo: rust-lang/rfcs#779 |
internal: Include toml files in the vfs Closes rust-lang#15753
It would be great if there was some table for showing functional equivalencies for common functions, ie. strdup, strtol, getenv
The text was updated successfully, but these errors were encountered: