FHY

Results 21 comments of FHY

More examples that reproduce the bug ![image](https://cloud.githubusercontent.com/assets/859740/8025618/e1844ed2-0d8e-11e5-8b4e-79c06fd0c3a6.png)

Sorry, it seems that the color for `==` is correct, the incorrect are the `>=` `/=` `

> Instead, it's a Subscriber with unspecified state, and you cannot use it except destroying it or re-assigning it. A moved Subscriber has unspecified state means that `~Subscriber()` has unspecified...

> It seems that you missed the sentence in the parentheses: unless otherwise specified. Some STL objects indeed ensure that the moved-from object will be in empty state (obviously, thread...

We almost missed the point, the point is about the default constructor rather than the moved state. 1. All the examples we talked about have default constructor. And that's how...

Thanks for following this topic that could be kinda esthetics-based. If I didn't get it wrong, 1. there are reasons not to use a default constructor != there is no...

> However, the designing philosophy of STL never mentioned that an STL class must have a default constructor. For example, some members in std::exception family do not have default constructor,...

> In fact, the compiler will construct the default constructor as needed。 @wb2712 No. The default contructor won't be generated if there are user defined constructor or a default constructor...