Explanation of [[nodiscard]] in C++17...

Why clang-tidy suggests to add [[nodiscard]] everywhere?...

How can I intentionally discard a [[nodiscard]] return value?...

What are the common practices and considerations for using the [[nodiscard]] attribute in C++ code?...

Why not apply [[nodiscard]] to every constructor?...

Why is the C++ standard library Container function empty() marked as [[nodiscard]]?...

Is there any benefit to tagging my class's constructor(s) as [[nodiscard]] when the class itself...

Implicit [[nodiscard]] for all const-tagged methods?...

Is [[nodiscard]] any different from [[gnu::warn_unused_result]]?...

Is it possible to ignore [[nodiscard]] in a special case?...

[[nodiscard]] attribute different compilation result for GCC and Clang...

[[nodiscard]] to a function pointer...

Does GCC 7.3 omit the [[nodiscard]] attribute for reference returning member functions?...

Are new C++17 [[nodiscard]] warnings since Visual Studio 15.6.2 compiler update standards-compliant?...

Is it right to use static_cast<void> to ignore iterator as return value?...

Why does [[nodiscard]] only encourage compiler to issue a warning and does not require it?...

Can I declare a type [[nodiscard]] with 'using'?...

Is nodiscard necessary on operators?...

Ways to specify [[nodiscard]] before C++17...

Why is unique_ptr::release not defined with [[nodiscard]]?...

Template parameter dependant [[nodiscard]]...

Trying out [[nodiscard]] with no success...

warning C5240: 'nodiscard': attribute is ignored in this syntactic position...

What is the rationale behind having [[nodiscard]] types?...

Why is std::move not [[nodiscard]] in C++20?...