Explore >> Select a destination
|
You are here 
|
sdowney.org | ||
| | | | |
donsbot.com
|
|
| | | | | I've been learning Rust for the past twenty days or so, working through the Blandy & Orendorff book, coding up things as I go. Once I got into playing with Rust traits and closures and associated types, the similarities to programming in Haskell with typeclasses, data structures, closure passing and associated types was pretty obvious.... | |
| | | | |
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: | |
| | | | |
verdagon.dev
|
|
| | | | | ||
| | | | |
ivelum.com
|
|
| | | What does it mean to be a full-stack web developer today, and what are their pros and cons for team productivity? | ||
