176
177
178
 
 

In c++17, std::any was added to t he standard library. Boost had their own version of "any" for quite some time before that.

I've been trying to think of a case where std::any is the best solution, and I honestly can't think of one. std::any can hold a variable of any type at runtime, which seems incredibly useful until you consider that at some point, you will need to actually use the data in std::any. This is accomplished by calling std::any_cast with a template argument that corresponds to the correct type held in the std::any object.

That means that although std::any can hold a type of any object, the list of valid objects must be known at the point that the variable is any_cast out of the std::any object. While the list of types that can be assigned to the object is unlimited, the list of types that can be extracted from the object is still finite.

That being said, why not just use a std::variant that can hold all the possible types that could be any_cast out of the object? Set a type alias for the std::variant, and there is no more boilerplate code than you would have otherwise. As an added benefit, you ensure type safety.

179
180
181
182
183
submitted 2 years ago by [M] to c/cpp@programming.dev
184
 
 

Please take 10 minutes or so to participate! A summary of the results, including aggregated highlights of common answers in the write-in responses, will be posted publicly here on isocpp.org and shared with the C++ standardization committee participants to help inform C++ evolution.

The survey closes in one week.

185
186
187
188
189
190
191
C++ STL Complexities (alyssaq.github.io)
submitted 2 years ago by [M] to c/cpp@programming.dev
192
193
194
195
submitted 2 years ago by to c/cpp@programming.dev
196
197
198
Reflection for C++26 (www.open-std.org)
submitted 2 years ago by [M] to c/cpp@programming.dev
199
submitted 2 years ago by [M] to c/cpp@programming.dev
200
view more: ‹ prev next ›