std::variant

Website: www.copperspice.com
Downloads: download.copperspice.com
Github: github.com/copperspice
Discussion: forum.copperspice.com

[@cyrilemeka6987]

Thank you very much❤

[@traveladdict8997]

Thank you for the intonation and clear presentation

[@aniliitb10]

I had gone through some tutorials earlier on std::variant but had never met std::monostate and wasn't familiar with non-intuitive behavior in case of array of chars. thanks for another quality tutorial.

[@CopperSpice]

I think std::monostate is not always part of the discussion. As you saw, it provides a standard compliant way of saying "nothing is here".

[@marlowa42]

This is an excellent presentation, thanks very much!

[@stormShadow64]

My godness, I love you both, great videos, btw both of you have amaizing voice ;)

[@CopperSpice]

Thank you so much. Comments like this help encourage us to keep producing these videos.

[@stormShadow64]

@@CopperSpice You are so great... Unlike lot of other online cpp sources, you do keep things simple and concise, most important topics in compressed way, the very great place to learn or rehearse one's knkwledge, wish you the best possible, and waiting impatiently for next video :) greetings from POLAND :)

[@CopperSpice]

@@stormShadow64, just in case you feel like coming to Wrocław we are presenting a talk at the code::dive conference in November. This will be our first visit to Poland and we are very excited.

[@TheMR-777]

*Many Thanks* , for such a *Great and Simplified Explanation* of this concept ..! I was searching for any good guide on *std::variant* , but almost no one compared it with unions with such a great precision. Comparing it with unions, with complete detail, was really a good idea! Now, a Programmer can decide, *"which to choose where?"* , which is quite difficult to teach, as a Teacher.

[@graham12345dd]

This is a great tutorial ! I'm subscribing! Thank you!

[@nicksklenicka8926]

Thank you!

[@JoshFlorii]

I don't know who you are but PLEASE keep this up!!!

[@CopperSpice]

Thanks for making us laugh, we asked ourselves the same question just the other day. We started the CopperSpice project several years ago as a set of cross platform libraries. It has expanded into DoxyPress and now these videos. Please check out our website, our github repos, and feel free to contact us with any questions.

[@experimentalhypothesis1137]

please make a video on std::invoke, std::visit, std::overload

[@userrand4900]

kzbin.info/www/bejne/fHe9fHttn7udo8k mentions that variant would result in a default constructed int with a random value. From experiments using clang, the value is always "0" vs. random. Which one is right?

[@fdwr]

13:02 Hmm, I'll never understand why the C++ committee made this interface so awkward to use, rather offering intuitive and discoverable methods. e.g. `std::get(v)` rather than simply `v.get()`, or the very wordy `std::holds_alternative(v)` rather than just `v.is_type()`, or lacking a way to get the index of a given type `v.index_of_type()`... It's fine to have the free functions too (just like std::data, std::begin, std::end...), but it would only help users to have methods that forwarded to the free functions. Until then, we can get tips from videos like this, and I'll use my 'fixed' version :). github.com/fdwr/TextLayoutSampler/blob/master/Common.Variant.h Cheers from Seattle.

[@CopperSpice]

All we can say is that we agree, the API is a bit awkward and it should be easier to use. We are working on some more examples to present in future videos.

[@climatechangedoesntbargain9140]

well, it would not be C++ anymore, would it?

[@TheMR-777]

@@climatechangedoesntbargain9140 That's why it's in *C++ 17 Standard* . All up to you, whether to use it or not.

[@climatechangedoesntbargain9140]

@@TheMR-777 ??

[@TheMR-777]

@@climatechangedoesntbargain9140 I mean, you can use the previous standards. But ... These features are for the people who already have worked in higher programming languages. They find difficulties while learning C++. For their ease, these features are made public. If I talk about us, we people who wanna be type-specific, we want perfection by any means. Even if have to write more code :), but we want perfection and precision.