@@mrdebug6581 cheers!

Thanks for the feedback, what is the timestamp? Using 'auto' is fine sometimes, probably varies on team culture on how it's used. format_string is a somewhat nasty alias, so I would probably recommend auto versus the underlying type: en.cppreference.com/w/cpp/utility/format/basic_format_string The comment section is otherwise useful for exchanging ideas, I'm curious if your team has any philosophy around auto?

​​​@@MikeShah the timestamp is 06:02. You used auto for the format strings, but it's absolutely not apparent what those types actually are. Which means, that when you had that compile error, someone with less knowledge would struggle to figure out what was wrong. Now I've been coding a long time, so I reckon auto probably defaulted to something like: const char* const format1 = "{} {}"; But as you can see, I'm literally just guessing because I've no idea what auto created for those types. That's the problem. I've no problem with auto being used in certain scenarios etc, especially to shorten declarations, such as: std::vector<uint8_t>::const_iterator iter = blah.begin(); Because in the above, it's obvious what iter is going to be if you removed that long type definition because it's equal to begin() which returns an iterator. However, where you used auto, you've no idea what the type is. It could be a char array or anything. In fact, if you'd been explicit with your type, you might not have made the mistake of not making it constexpr. As for my personal opinion of auto, it's this... Being explicit is in the majority of cases better than using auto. Firstly, someone can immediately see what the type is without having to guess what auto is going to generate. Secondly, if a type ever changes auto could hide that error from you. Being explicit would generate a compile time error whilst with auto it might compile and now you're having to do some serious debugging. Lastly, I've found myself recently working on a really old codebase where there is no constexpr or auto and although this video is focusing on C++ 23 features, an explicit declaration would have compiled on any C++ standard. Auto serves a purpose, sure, but I tend to use it ONLY when it's completely clear what type it's going to yield and there's no risk of it being mutated into something else.

@@finlaymetcalfe6360 we will eventually texture a quad in this series 🙂

Indeed, I think you might be right -- GLM flipped these at some point -- I think it was radians by defualt, or I had otherwise defined them as such: glm.g-truc.net/0.9.4/api/a00151.html#ga283629a5ac7fb9037795435daf22560f . Very nice job on the new series!

@@tanveerasif5978 cheers!

I have a System76 Heavy

Indeed, that is correct! Because say a corner of a cube for example, each vertex will be a part of 3 faces, thus need 3 unique normals for each face. Many tools will otherwise give the option to 'average vertex normals' and just emit one normal per-vertex, but it just depends on what type of lighting you need.

Cheers! I have not -- it was a mix of visualization tools and program analysis. I have some videos of LLVM burried away on my channel somewhere that provide introductions to some of the program analysis stuff for getting started otherwise.

Cheers!

Interesting -- thanks for sharing!

Working through this series will get you started with the language. Later on we work with the 'STL' containers which are data structures and the 'STL' algorithms. As of now, I do not have a Data Structure and Algorithm (DSA) series -- but I am planning one in the future.

@@MikeShah i really like the series, thank you so much

@@rishi-cl2xr Cheers!

Cheers -- welcome aboard! There's no specific book for the series, but I have some recommendations here: kzfaq.info/get/bejne/Z8h_hLdqsNalf6c.html I might recommend either 'Tour of C++' or 'C++ Game Programming' from the video as nice videos to read and supplement what you learn in this playlist, which you can watch in a linear order.

Sorry. It's just too much. Can't watch a video where every few seconds someone says, "go ahead and..." It's far too distracting!

Cheers, thank you for the kind words!

Cheers!

Indeed, I saw this on Twitter -- I haven't seen the videos yet though.

Agreed !

We're approaching episode 100 soon 😁

Sorry about that -- one reason I do keep my terminal dark is to help ease on the eyes. I think everyone has different preferences on this though.

@@MikeShah to be fair, it was made worse because I was watching at 11pm or so in the dark. I'll give it another go in daylight and I expect it'll be better =)

@@DarenC Many of us have been known to code late into the night 😁

@@purpletom_yt3138 cheers!

Cheers!

I'll have to do a proper test with optimizations and using the LDC2 compiler in D. I suspect it will be very fast😀

I think so -- the next few videos are about code refactor -- so how we go from a 'triangle' to start building a framework for more general purpose use.

@@MikeShah thanks! Im going to sleep now i think

Indeed!

Time will tell!

Cheers -- more coming this week!

You can always make a raw array 'static' to zero-initialize it, as that memory needs to be reserved. I haven't covered 'constinit' yet, but that can be helpful to gaureentee static initialization. Otherwise, the use of 'constexpr' can shine here for compile-time execution, and filling in your array :) Perhaps this is a separate video in the future.

@@MikeShah tnx❤

Cheers! That's a nice idea -- I have some materials on this for C++, so I can consider a video like this in the future

Agreed -- mesh is something most folks know. Neat if non-programmers are also learning uniforms, they're way ahead of me when I was just playing games then :)

C3 as I understand is still under active development. There may be projects using C3, but have not otherwise disclosed -- sometimes it's a competitive advantage not to give away your toolstack for companies.

@@MikeShah thx

Cheers! 3 more videos coming this week in my opengl graphics series 🙂

Cheers! Indeed, works like the unix command 'uniq' removing adjacent values :)

@@duncangibson6277 that's where we're heading 😁

Unfortunately I have not done much in the embedded space in some time. There's a specific conference for C++ and embedded space that otherwise has resources: embo.io/

@@TimHaga cheers!

Cheers, thank you for the kind words!

There's a trick you can use with templates to get the decltype of a type. See stackoverflow.com/questions/16637945/empirically-determine-value-category-of-c11-expression

It's an attempt to manage the 'noise' in learning the graphics API. Many folks are also following along this series in other languages that do not use unique_ptr 🙂Perhaps towards end of series I will do a larger refactoring to modernize the code.

Cheers -- episode 36 is hot of the presses today! kzfaq.info/get/bejne/a618YJZz28rKaJs.html

For larger projects I do

Cheers!

Cheers!