Explore >> Select a destination
|
You are here 
|
www.think-cell.com | ||
| | | | |
dvratil.cz
|
|
| | | | | Thank you to everyone who reported issues and contributed to QCoro. Your help is much appreciated! Support for awaiting Qt signals with QPrivateSignal Qt has a feature where signals can be made "private" (in the sense that only class that defines the signal can emit it) by appending QPrivateSignal argument to the signal method: class MyObject : public QObject { Q_OBJECT ... Q_SIGNALS: void error(int code, const QString &message, QPrivateSignal); }; QPrivateSignal is a type that is defined inside the Q_OBJECT macro, so it's private and as such only MyObject class can emit the signal, since only MyObject can instantiate QPrivateSignal: | |
| | | | |
lapinozz.github.io
|
|
| | | | | My goodbye to template metaprogramming. One last tribute; computing A Star pathfinding algorithm at compile-time | |
| | | | |
rodusek.com
|
|
| | | | | Getting the name of a type in C++ is a hassle. For something that should be trivially known by the compiler at compile-time, the closest thing we have to getting the type in a cross-platform way is to use std::type_info::name which is neither at compile-time, nor is it guaranteed to be human-readable. In fact, both GCC and Clang actually return the compiler's mangled name rather than the human-readable name we are used to. Let's try to make something better using the modern utilities from c++17 and a little creative problem solving! | |
| | | | |
mrcat.au
|
|
| | | I've started learning Zig, a new programming language in the same problem space as C, and it has some features I really like. While it's not memory-safe in the Rust way, it has a lot of compile time and runtime checks to prevent common footguns. It has packed structs and variable-width integers to allow for easy parsing of bitpacked binary formats. Its comptime metaprogramming capabilities are spectacular. And it even interoperates seamlessly with C! | ||
