Available as a drop down within the configure graphics tab.

Same behavior, but without the need to explicitly loop through
everything manually.

Simplifies the overall function and also allows for it to become a
const-qualified member function.

Aligns the '=' to be consistent with the rest of the logs within this
source file.

A formatting specifier within Clear wasn't being used, which will cause
fmt to throw an exception. This fixes that.

We can just use the kernel member variable directly instead of going
through the system to obtain the same thing.

- Necessary for multiple service threads.

- This was holdover from citra.

Removes bounds checking from "texceptions" instances.

OpenGL core defaults to GL_POINT_SPRITE, meanwhile on OpenGL
compatibility we have to explicitly enable it. This fixes
gl_PointCoord's behaviour.

Previously the UDP backend would never actually get shut down.

Prevents trivial warnings and ensures interfaces are properly
maintained between the base class.

std::function is allowed to heap allocate if the size of the captures
associated with each lambda exceed a certain threshold. This prevents
potentially unnecessary reallocations from occurring.

Gets rid of a trivially avoidable atomic reference count increment and
decrement.

Future-proofs code if boost is ever updated.

Amends the constructor initializer list to specify the order of its
elements in the same order that initialization would occur.

Shifts a pair of registers to the right and returns the low register.

Shifts a pair of registers to the left and returns the high register.

Now both CPU backends go through their referenced system instance to
obtain the current thread.

shared_ptr was used in 2d1984c2 due to a
misunderstanding of how the language generates move constructors and
move assignment operators.

If a destructor is user-provided, then the compiler won't generate the
move constructor and move assignment operators by default--they must be
explicitly opted into.

The reason for the compilation errors is due to the fact that the
language will fall back to attempting to use the copy constructor/copy
assignment operators if the respective move constructor or move
assignment operator is unavailable.

Given that we explicitly opt into them now, the the move constructor and
move assignment operators will be generated as expected.

Nothing from these headers are used within this source file, so we can
remove them.

This isn't used within the class, so it can be removed to simplify the
overall interface.

While we're in the same area, we can simplify a unique_ptr reset() call.