Explore >> Select a destination
|
You are here 
|
josiahparry.com | ||
| | | | |
jmmv.dev
|
|
| | | | | Dependency injection is one of my favorite design patterns to develop highly-testable and modular code. Unfortunately, applying this pattern by taking Rust traits as arguments to public functions has unintended consequences on the visibility of private symbols. If you are not careful, most of your crate-internal APIs might need to become public just because you needed to parameterize a function with a trait. Let's look at why this happens and what we can do about it. | |
| | | | |
r-spatial.github.io
|
|
| | | | | Read simple features from file or database, or retrieve layer names and their geometry type(s) Read PostGIS table directly through DBI and RPostgreSQL interface, converting Well-Know Binary geometries to sfc | |
| | | | |
coredumped.dev
|
|
| | | | | Updated: 2023-01-06 About a year ago I was bitten by the PL bug. It started with reading Crafting Interpreters and discovering the wonders hidden under the hood of a compiler. I am also been a big fan of Emacs, and this started to get me interested in how its interpreter works. At the same time, I was reading the Rust book and trying to understand the concepts there. This all came to a head, and I decided to write an Emacs Lisp interpreter called rune in Rust. | |
| | | | |
www.shuttle.rs
|
|
| | | What makes Rust worth using for backend web services? | ||
