Standard Template Library (C++)
Hey guys! Currently I'm making a tutorial on STL containers (std::vector, std::list, std::etc.), and I think I might publish it around next week.
So does anyone have any suggestions of things to include? I'm definitely going to be going over the basic STL containers, along with some useful tips and algorithms. But is there anything different you guys will want to see?
Please let me know in the comments. Thanks, and see you next week!
UPDATE: It's released!
You should try to include cool things like
I looove pointers
it’s funny, cause all us C++ programmers love pointers, and the only real reason that I ever really read about for ppl not to like C++ is because of pointers.. lol
Anyways Idk bout that. The point is to reduce the likelihood of bugs like memory leaks and stuff, yes? I guess the reason I personally don’t like them is more because I’m really nervous all the time about using STL containers, because I’m never entirely sure how they will act in certain vital situations. I guess I’m just too lazy to look it up?
Things I’d really like to see in order of preference...
1) std::multimap // because I am so confused by how it’s supposed to / does work
2) std::tuple // because it’s amazing
3) std::any // because it’s amazing
@Highwayman Oh yeah for sure, I'll be covering maps, multimaps, unordered maps, and all those. For
std::tuple, I'm not really an expert on that, but I know enough about the basics, so I'll try to fit that in as well. And for
std::any, I'm not really an expert on any of the new C++17 features, as I'm learning C++14, but I'll try my best to include that as well. Thanks for the suggestions!
For sure keep vectors, lists. Introduce stream writing and list sorting. If you know how, which I bet you do, go over dynamic casting and smart pointers. Good Luck!
@nt998302 Thanks for your reply! I'm going to cover all the main STL containers, lists, maps, deques, sets and more. But don't you think that stream writing, dynamic casting, and smart pointers are for another tutorial? I kinda just want to stick with lists for this tutorial, otherwise it'll be a mess to write
@nt998302 Oh that's cool! I actually tried learning Unreal for a couple of weeks, and I really liked making abandoned structures and forests and those "nature" scenes. But I totally agree, making games in Unreal using C++ is a little too complicated. However I really want to learn Unity and C# like you did, but I also kinda want to "finish" learning C++ first...
Oh, hey guys, quick questions. So I'm writing the tutorial on Google Docs right now, and the section about vectors is already 1000 words long. And I still have to talk about lists, sets, mutisets, maps, and more! Should I post each section separately? Or will a giant long tutorial do?