Explore >> Select a destination
|
You are here 
|
blog.burntsushi.net | ||
| | | | |
adventures.michaelfbryan.com
|
|
| | | | | In a project Ive been playing around with recently, weve encountered the dilemma where you want to make it easy for users to write their own application logic using the system but at the same time want to keep that logic decoupled from the implementation details of whatever platform the application is running on. If youve been programming for any amount of time your immediate reaction is probably why bother mentioning this, doesnt it just fall out of good library design? | |
| | | | |
dygalo.dev
|
|
| | | | | Sometimes we need to extend existing Python projects with other languages to solve performance issues or to include some functionality already written in another language. In this chapter, we will create a full-featured Python integration for a Rust crate we built in the previous article. As the primary goal, I want to focus on a pleasant end-user experience and share tips on improving the usability and debuggability of the resulting library. | |
| | | | |
nick.groenen.me
|
|
| | | | | After working through "the book" on the Rust programming language and getting started with the first non-trivial, real-world application I found myself faced with a question I didn't yet feel well-equipped to handle: "How should you structure error handling in a mature rust application?" | |
| | | | |
blog.skylight.io
|
|
| | | One of the coolest features of Rust is how it automatically manages resources for you, while still guaranteeing both safety (no segfaults) and high performance. Because Rust is a different kind of programming language, it might be difficult to understand what I mean, so let me be perfectly clear: * In | ||
