Explore >> Select a destination
|
You are here 
|
billwadge.com | ||
| | | | |
weblog.raganwald.com
|
|
| | | | | ||
| | | | |
www.pl-enthusiast.net
|
|
| | | | | This post covers the third quarter of CS 330, UMD's programming languages course, in particular material on formal language theory and language semantics. | |
| | | | |
www.pl-enthusiast.net
|
|
| | | | | This post describes the structure, goals, and content of CMSC 330, UMD's sophomore-level programming languages course. This is part 1. | |
| | | | |
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. | ||
