Serves no actual purpose in this instance besides making NACP's copy assignment deleted, which is not intended behavior.

Allows these functions to compile when T is not u8.

renderer_opengl: Correct forward declaration of FramebufferLayout

configure_per_general: Mark UI strings as translatable in the constructor

configure_input_simple: Make input profile array constexpr

These are user-facing strings, so they should be translatable.

Calling tr() from a file-scope array isn't advisable, since it can be
executed before the Qt libraries are even fully initialized, which can
lead to crashes.

Instead, the translatable strings should be annotated, and the tr()
function should be called at the string's usage site.

This is actually a struct, not a class, which can lead to compilation
warnings.

* Fixed shader linking error due to TLDS

coord should be coords

* Fix remaining coords

svc: Implement SetThreadActivity (thread suspension)

shader_bytecode: Fixup TEXS.F16 encoding

Port citra-emu/citra#4164: "citra_qt, video_core: Screenshot functionality"

common/quaternion: Ensure that w is always initialized

am: Implement HLE profile selector applet

configure_input: Add Controller Setup Profiles and simplify input UI

Previously xyz was always being zero initialized due to its constructor,
but w wasn't. Ensures that we always have a deterministic initial state.

Fixed uninitialized memory due to missing returns in canary

Texture format fixes for RGBA16UI for copies and R16U when used as depth

kernel/{process, thread}: Amend behavior related to IDs

service/am: Unstub GetAppletResourceUserId

Device handle should not be a random id, instead it's the current npad id

Fix arrayed texture LOD selection and depth comparison ordering

service/sm: Improve debug log for RegisterService

If a thread handle is passed to svcGetProcessId, the kernel attempts to
access the process ID via the thread's instance's owning process.

Technically, this function should also be handling the kernel debug
objects as well, however we currently don't handle those kernel objects
yet, so I've left a note via a comment about it to remind myself when
implementing it in the future.

kernel/svc: Implement svcSetMemoryAttribute

With all the basic backing functionality implemented, we can now unstub
svcSetMemoryAttribute.

This puts the backing functionality for svcSetMemoryAttribute in place,
which will be utilized in a following change.

vm_manager: Add member function for checking a memory range adheres to certain attributes, permissions and states

Starts the process ID counter off at 81, which is what the kernel itself
checks against internally when creating processes. It's actually
supposed to panic if the PID is less than 81 for a userland process.

The service call uses a 64-bit value, just like svcGetProcessId. This
amends the function signature accordingly.

The kernel uses a 64-bit value for the thread ID, so we shouldn't be
using a 32-bit value.

svcGetProcessId's out parameter is a pointer to a 64-bit value, not a
32-bit one.

In the actual kernel, this is a 64-bit value, so we shouldn't be using a
32-bit type to handle it.

Found during hardware testing

Functions which are suppose to crash on non canary builds usually don't return anything which lead to uninitialized memory being used.

Now it also indicates the name and max session count. This also gives a
name to the unknown bool. This indicates if the created port is supposed
to be using light handles or regular handles internally. This is passed
to the respective svcCreatePort parameter internally.