Explore >> Select a destination
|
You are here 
|
adamstorr.co.uk | ||
| | | | |
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. | |
| | | | |
www.devjoy.com
|
|
| | | | | Site template made by devcows using hugo | |
| | | | |
vannevel.net
|
|
| | | | | With the release of Visual Studio 2015 RC, we also received the pretty much final implementation of the Diagnostics implementation. This SDK allows us to create our own diagnostics to help us write proper code that's being verified against those rules in real-time: you don't have to perform the verification at a separate build-step. What's more is that we can combine that with a code fix: a shortcut integrated in Visual Studio that provides us a solution to what we determine to be a problem. | |
| | | | |
johannesbrodwall.com
|
|
| | | |||
