Rust Search
Find the best content on Rust, curated by the community; a
search engine for Rustaceans.
The goal of this talk is to provide an introduction to the gtk bindings in Rust through the gtk-rs organization. It'll be mainly about how we made it and how we keep making it better. Presentation of gtk-rs (before it was even an organization) Beginning: rust <-> C direct binding, no indirection, almost no safety Generation of signals through (old) macro system Old closures system to allow callbacks Short (old) code demonstration Creation of gtk-rs multi-repository easier to maintain, more difficult to release licensing issues: keeping docs in their own repository and write a tool to put it back New gtk-rs era: automatic generation GIR crate Parsing gir files and automatically generate as much as possible Presentation of the crate, how it works and the hierarchy A lot of things are simplified: doc generation, website, releases gtk-rs growth more members (semi) automatic release process a lot more of bindings (sourceview, pangocairo, webkit...) gtk-rs environment a few projects (process viewer, EDI, tools...) relm crate to easily write GTK UIs GNOME-class gstreamer-rs Future of gtk-rs async tutorials more projects more rust in GNOME libraries (librsvg already started this port)
A quick introduction to the unique memory management concepts of Rust.
Rust is a big language and it gets bigger every day. Many beginners ask: "What is idiomatic Rust?". This talk will highlight simple tips to make your Rust code more elegant and concise, and introduce you to my peer-reviewed collection of articles/talks/repos for writing idiomatic Rust code.
Today, many new programming languages have been created in order to simplify at the extreme the art of programming (Golang), to boost the performance of their human readable application (Nim), to secure the way to make and run programs with zero-cost abstraction (Rust), or just to propose a new exiting way to write programs (Scala, Swift), etc. Each of those new programming languages has its own features, goals, attendance, and community. Today, it may become hazardous to develop with a new programming language, especially for a company or for a full-time personal project, due to the lack of stability, libraries, IDE features for this programming language, a too small or strict community, or many other obvious reasons. The goal of this presentation is to introduce the concepts of Rust, its pros and cons, and how Rust differs from the others programming languages. The target audience is mainly for developers who are reluctant to launch themselves into Rust, or project managers and CTOs who are looking for stable and exciting new technologies. This talk is intended to emphasize Rust rationale, and will explain clearly and precisely why Rust wants to be the programming language of the next ten years.
"I think in general "force the user to think about the extra cases, and be explicit about ignoring them" is definitely idiomatic rust."