While admirable as a means to ensure immutability, this has the
unfortunate downside of making the class non-movable. std::move cannot
actually perform a move operation if the provided operand has const data
members (std::move acts as an operation to "slide" resources out of an
object instance). Given Barrier contains move-only types such as
std::mutex, this can lead to confusing error messages if an object ever
contained a Barrier instance and said object was attempted to be moved.

Simplifies the constructor interfaces for Barrier and Event classes.

Keeps the non-member interface in one spot instead of split into two
places, making it nicer to locate functions.

This is also unused and superceded by standard functionality. The
standard library provides std::this_thread::sleep_for(), which provides
a much more flexible interface, as different time units can be used with
it.

This is an old function that's no longer necessary. C++11 introduced
proper threading support to the language and a thread ID can be
retrieved via std::this_thread::get_id() if it's ever needed.

Use default values for unknown framebuffer pixel format

gl_shader_decompiler: Use UNIMPLEMENTED when applicable

am/applets: Minor cleanup

gl_shader_decompiler: Remove UNREACHABLE when setting RZ

common/math_util: Minor cleanup

common: Remove depencency on xbyak

Xbyak is currently entirely unused. Rather than carting it along, remove
it and get rid of a dependency. If it's ever needed in the future, then
it can be re-added (and likely be more up to date at that point in
time).

Gets rid of the need to use typename to access the ::type alias.

Allows objects that contain rectangle instances to be constexpr
constructible as well.

const/constexpr variables have internal linkage by default.

This hasn't been used since the project started, so we may as well get
rid of it to keep it from bit rotting.

maxwell_3d: Initialize rasterizer color mask registers as enabled.

am: Correct build failure

- Fixes rendering regression with Sonic Mania.

The interface for shared memory was changed, but another commit was
merged that relied on the (previously public) internals of SharedMemory.

This amends that discrepancy.

kernel/shared_memory: Make data members private, plus minor interface changes

ldr: Clean up error codes

kernel/process: Move <random> include to the cpp file

common/assert: Make the UNIMPLEMENTED macro properly assert

file_sys/card_image: Provide named members for the GamecardInfo struct

Fills out the struct according to information provided by SwitchBrew

Currently, there's no way to specify if an assertion should
conditionally occur due to unimplemented behavior. This is useful when
something is only partially implemented (e.g. due to ongoing RE work).
In particular, this would be useful within the graphics code.

The rationale behind this is it allows a dev to disable unimplemented
feature assertions (which can occur in an unrelated work area), while
still enabling regular assertions, which act as behavior guards for
conditions or states which must not occur. Previously, the only way a
dev could temporarily disable asserts, was to disable the regular
assertion macros, which has the downside of also disabling, well, the
regular assertions which hold more sanitizing value, as opposed to
unimplemented feature assertions.

Currently, this was only performing a logging call, which doesn't
actually invoke any assertion behavior. This is unlike
UNIMPLEMENTED_MSG, which *does* assert.

This makes the expected behavior uniform across both macros.

<random> isn't necesary directly within the header and can be placed in
the cpp file where its needed. Avoids propagating random generation
utilities via a header file.

The accessor should be doing just that, accessing, rather than retaining
the lifetime of the data broker as well.

Also resolve places where includes should have been provided, but
weren't.

Avoids wonky wrapping and makes it nicer to read.

am: Implement HLE software keyboard applet

lm: Implement SetDestination by doing nothing

kernel/resource_limit: Clean up interface

Cleans out the citra/3DS-specific implementation details that don't
apply to the Switch. Sets the stage for implementing ResourceLimit
instances properly.

While we're at it, remove the erroneous checks within CreateThread() and
SetThreadPriority(). While these are indeed checked in some capacity,
they are not checked via a ResourceLimit instance.

In the process of moving out Citra-specifics, this also replaces the
system ResourceLimit instance's values with ones from the Switch.

This service function was likely intended to be a way to redirect where
the output of a log went. e.g. Firing a log over a network, dumping over
a tunneling session, etc.

Given we always want to see the log and not change its output. It's one
of the lucky service functions where the easiest implementation is to
just do nothing at all and return success.