A show about the Rust programming language and the people who use it.
A story and a dream (and the promise of Rust): the final episode of New Rustacean!
(Thanks to the couple people donating who opted out of the reward tier, as well. You know who you are!)
WASI, Option::copied, and the future of async/await syntax!
Thanks to Parity for sponsoring the show and hiring Rust developers!
(Thanks to the couple people donating who opted out of the reward tier, as well. You know who you are!)
Automatic generation of FFI types between Rust and C APIs.
Thanks to Parity for sponsoring the show and hiring Rust developers!
(Thanks to the couple people donating who opted out of the reward tier, as well. You know who you are!)
Exposing Rust types and functions to C API consumers.
It’s impossible to make the declarations below follow the order I talked through them on the recording without also making them horrible to read, so just use this outline instead:
Thanks to Parity for sponsoring the show and hiring Rust developers!
(Thanks to the couple people donating who opted out of the reward tier, as well. You know who you are!)
Item visibility and pub(<restricted>) as API design tools.
The easiest and most effective way to understand the example in this case will simply be to look directly at the source code. You can read the docs for each of the nested modules, but you’ll be doing a lot of navigating around for that.
Also, I am using Cargo’s --document-private-items flag, so that you can see all the items in all the modules, even those which are not public, but note that usually you would not see docs for those!
Thanks to Manning for sponsoring the show and giving all of you a 40%-off discount on their whole store (but especially their WebAssembly in Action MEAP) at deals.manning.com/new-rustacean!
(Thanks to the couple people donating who opted out of the reward tier, as well. You know who you are!)
Moar const fn, some Pin, and alternative Cargo registries!
Thanks to Parity for sponsoring the show and hiring Rust developers!
(Thanks to the couple people donating who opted out of the reward tier, as well. You know who you are!)
Using Rust’s Foreign Function Interface (FFI) with C!
The code samples here directly match the things I described in the show, so you will likely want to look at add and ffi::add, then Point, translate, and ffi::translate in that order.
Other helpful Rust FFI discussions:
Thanks to Manning for sponsoring the show and giving all of you a 40%-off discount on their whole store (but especially Carol Nichols’ and Jake Goulding’s Rust in Motion video content and the Rust in Action MEAP!) at deals.manning.com/new-rustacean
(Thanks to the couple people donating who opted out of the reward tier, as well. You know who you are!)
How I make the show, and why you won’t find it on Google Play, Spotify, or Stitcher.
Thanks to Parity for sponsoring the show and hiring Rust developers!
(Thanks to the couple people donating who opted out of the reward tier, as well. You know who you are!)
A story about parsing command-line arguments manually and some thoughts on “rookie mistakes.”
Thanks to Parity for sponsoring the show and hiring Rust developers!
(Thanks to the couple people donating who opted out of the reward tier, as well. You know who you are!)
Associated items: functions and methods, constants, types, and (very briefly!) GATs.
Thanks to Manning for sponsoring the show and giving all of you a 40%-off discount on their whole store (but especially Carol Nichols’ and Jake Goulding’s Rust in Motion video content and the Rust in Action MEAP!) at deals.manning.com/new-rustacean
(Thanks to the couple people donating who opted out of the reward tier, as well. You know who you are!)
dbg!, unified paths, more places you can use Self, and a bunch of const fn stabilizations—plus some neat community highlights!
Thanks to Parity for sponsoring the show again. Go check out their Rust jobs!
(Thanks to the couple people donating who opted out of the reward tier, as well. You know who you are!)
Your feedback is valuable to us. Should you encounter any bugs, glitches, lack of functionality or other problems, please email us on [email protected] or join Moon.FM Telegram Group where you can talk directly to the dev team who are happy to answer any queries.