Hola de rustacianos,
I am writing from the aftermath of the rustfest in barcelona. I "apologize" for not writing my common theme based message since I am currently at the airport waiting for my flight back to vienna. So I didn't have the time to write something creative.
We have some nice talks coming up which I am really happy to announce.
Lorzenz Leutgeb a software engineer from Sclable
*canceled due to technical reasons -> never change a running system*
My First Rust Project: Eyetracking for Human-Computer Interaction
Did the tendons in your forearm ever hurt from using your mouse too much? Are you annoyed about the inefficiency when your index finger must leave home row to travel to the touchpad? What if your computer would be aware of where you are looking and the rotation of your head, so that moving the cursor is faster than the blink of an eye? I experimented and came up with a prototype that bundles an eyetracking device and a gyroscope mounted on headphones to deliver this exotic interface. All the glue code was hacked in Rust.
What part of Hindley-Milner do you not understand?
Most of us have spent some time deciphering rustc messages talking about type errors. Some of you might have seen that they are similar to ghc errors. I will shed some light on the similarities of Rust's, Haskell's and similar type inference/system by introducing their theoretical ancestor
Lorenz is a software engineer passionate about programming languages and formal methods in computer science.
And one of our much appreciated regulars who shines with competence and stoic dry humor ;)
Using C-Libraries in Rust
Writing pure Rust code is great, but if you want to talk to an existing ecosystem or just system libraries, you can't avoid interfacing with C libraries. For most C libraries, there's a nice crate out there, but what if there isn't one?
The presenter of this talk experienced just this situation with the Chromium Embedded Framework, which is probably one of the largest C/C++ APIs out there. This talk will take the learnings from this task to show how you can interface with C libraries, including the pitfalls and challenges you might experience while doing so. It will also explain how to use unsafe Rust to simulate the behavior of C code in order to achieve the crazy things C libraries expect their callers to do for memory management. The ultimate goal is to create a safe Rust wrapper around these to optionally be released on crates.io.
We're looking forward seeing you women and guys :)