/explore
|
You are here 
|
eyakubovich.github.io | ||
| | | | |
www.foonathan.net
|
|
| | | | | Just like regular function parameters, template parameters can also have default parameters. For class templates, this behaves mostly just like default function arguments: if you pass fewer template arguments than required, default template arguments are used to fill the remaining places. However, for function templates, it gets more complicated as template parameters for functions can be deduced by the normal function arguments. This leads to some interesting side-effects. In particular, default argumen... | |
| | | | |
articles.bchlr.de
|
|
| | | | | [AI summary] The article discusses challenges and workarounds for upcasting trait objects in Rust, exploring the limitations of dynamic dispatch and potential solutions through vtable structures and custom trait implementations. | |
| | | | |
www.sandordargo.com
|
|
| | | | | Recently, in the binary sizes series, we discussed how run-time type information affects RTTI. I also mentioned that in my opinion the lack of RTTI leads to better practices and you'll end up with a more readable, more maintainable code. It's time to delve into this topic and see why. What is RTTI again? But first of all, let's quickly recap what is run-time type information. RTTI let us have information on the dynamic type of reference/pointer types. It lets us use dyanamic_casts and also call the typeid() function and query the returned instance of std::type_info. I think that not having access to these tools will let you write better code. Why so? Let's start with probably the less controversial tool. Don't rely on typeid() Inexperienced programmers might... | |
| | | | |
solarianprogrammer.com
|
|
| | | How to compile from sources GCC 10 on macOS Catalina | ||
