expected VS GLM

On this topic Sy Brand is a guarantee, in fact he did the https://github.com/TartanLlama/expected and several presentation of the subject.

In the meantime, I may use the TartanLlama implementation (here) and plan around replacing it with the real deal in the near future.

Sy Brand's tl::expected

expected is my favourite little part of cpp23, I’m using it often in codebase with https://github.com/TartanLlama/expected 😁

outcome and/or expected

Eventually you'll be able to use std::expected in C++23!

https://en.cppreference.com/w/cpp/header/expected

Don't throw exceptions, require the caller to handle errors and propagate them up the stack (everything returns an expected) if they cannot be handled. You are forced to model the error domains instead of just throwing an exception and assuming the caller knows to catch it and do something with it.

Java has checked exceptions, but, Kotlin decided to abandon them.

The nice codebases I have worked on stick to the Result type in Swift or Kotlin. And thus you are forced to 'translate' errors (exceptions?) as described in Alan Griffith's 'Exceptional Java'.

https://accu.org/journals/overload/10/48/griffiths_406/

"If a checked exception is thrown (to indicate an operation failure) by a method in one package it is not to be propagated by a calling method in a second package. Instead the exception is caught and "translated". Translation converts the exception into: an appropriate return status for the method, a checked exception appropriate to the calling package or an unchecked exception recognised by the system. (Translation to another exception type frequently involves "wrapping".)"

If you can't wait for C++23, there's a single header implementation here.

https://github.com/TartanLlama/expected

I am a greenhorn at graphics programming. I just made an app in OpenGL with C++ that I now need to change over to a browser app with WebGL. WebGL looks pretty cool but since my app does a lot of calculations I assumed I should keep the heavier calculating parts in C++ with emscripten ( which I am also just learning ). So looking at it, it just looks like glm is the only library I seriously need for my c++ code and that seems pretty cool because it is a header only app it says. But in the github there are a lot of folders and files so I am not sure which are indispensable or not. Any advice?

GLM does it quite well, it has core includes then a detail folder with all the inl files that get added. https://github.com/g-truc/glm

I once ported an OpenGL code base over to Metal. For me, it was essential to do as much code sharing as possible. Because I was using the GLM library in that code base and generally found that library very useful I wanted to know whether I can use GLM with Metal. I had to do some research but it turned out it works really well, see here

I would also recommend GLM

Alongside MiniEngine, you’ll want to look into the DirectX Toolkit. This is a set of utilities by Microsoft that simplify graphics and game development. It contains libraries like DirectXMesh for parsing and optimizing meshes for DX12, or DirectXMath which handles 3D math operations like the OpenGL library glm. It also has utilities for gamepad input or sprite fonts. You can see a list of the headers here to get an idea of the features. You’ll definitely want to include this in your project if you don’t want to think about a lot of these solved problems (and don’t have to worry about cross-platform support).