Explore >> Select a destination
|
You are here 
|
jguegant.github.io | ||
| | | | |
www.reedbeta.com
|
|
| | | | | Pixels and polygons and shaders, oh my! | |
| | | | |
cplusplus.github.io
|
|
| | | | | ||
| | | | |
www.bfilipek.com
|
|
| | | | | The ISO Committee accepted and published the C++17 Standard in December 2017. In this mega-long article, I've built (with your help!) a list of all major features of the new standard. Please have a look and see what we get! Language Features New auto rules for direct-list-initialization static_assert with no message typename in a template template parameter Removing trigraphs Nested namespace definition Attributes for namespaces and enumerators u8 character literals Allow constant evaluation for all non-type template arguments Fold Expressions Unary fold expressions and empty parameter packs Remove Deprecated Use of the register Keyword Remove Deprecated operator++(bool) Removing Deprecated Exception Specifications from C++17 Make exception specifications pa... | |
| | | | |
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. | ||
