This renames the Mutex class member functions so that the mutex types
satisfy Lockable.
This makes them usable with standard std::scoped_lock
and std::unique_lock, which lets us use RAII and avoids the need
for a custom RAII wrapper :)
* Stratosphere: Use modern C++ idioms in some places
* algorithms like std::for_each are used instead of raw loops
* Stratosphere: Replace more raw loops with algorithms
* Stratosphere: Add a utility predicate function to test for equality with a reference element
This can be used to rewrite some common raw loops using algorithms instead
* fs.mitm: Use variant
* fs.mitm: Use enum class
* fs.mitm: Turn RomFSSourceInfo::Cleanup into a destructor
This obsoletes the need for a custom deleter in other places
* fs.mitm: Use enum class some more
* fs.mitm: Use unique_ptr
* fs.mitm: Simplify initialization
* Stratosphere: Simplify initialization
* fs.mitm: Use unique_ptr (fix memory leak along the way)
The previous code was using "delete" rather than "delete[]"
* fs.mitm: Use vector::emplace_back rather than push_back
emplace_back constructs elements in-place, hence avoiding a redundant element copy.
* Stratosphere: Replace more raw loops with algorithms
* Stratosphere: Use unique_ptr
* fs.mitm: Replace more raw loops with algorithms
* Stratosphere: Prefer move-construction over copy-construction when moving sink parameters around
* boot2: Simplify g_additional_launch_programs
It appears that Stratosphère is targeting C++17. In C++17,
std::make_tuple is not required for initialisating a tuple anymore.
Same thing, but less typing
* Replace std::make_tuple with {}
More readable and less noise. Also fixes two missing return statements.
f(x, x++) is unspecified behaviour in C++. An implementation could
evaluate arguments from left to right or from right to left.
`T(r.Buffers[a_index], r.BufferSizes[a_index++])` might
access the wrong buffer if `a_index++` is evaluated before the first
argument.
Fixes -Wsequence-point warnings
