Removing this as we don't enforce unused parameter warnings elsewhere in the project, and explicitly specify -Wno-unused-parameter in the main CMakeLists.

Now that the entire project is free of variable shadowing, we can enforce this as a compile time error to prevent any further introduction of this logic bug.

GCC/Clang treats variables within lambdas as potentially shadowing those outside the lambda, despite them not being captured inside the lambda's capture list.

core/debugger: support operation in yuzu-cmd

core/debugger: allow remote connections

kernel: fix KCodeMemory initialization

gdbstub_arch: Add missing virtual destructor

The class is used polymorphically, so it's undefined behavior to delete
instances of GDBStubA64 and GDBStubA32 from the base class pointer.

log the MSVC runtime version when running on MSVC build

deprecate usage of QDesktopWidget for going fullscreen

retranslate the game list placeholder

gpu_thread: Move to bounded queue

general: Set renderer_backend's default to Vulkan

This might be useful information, not 100% sure.

[   0.958068] Frontend <Info> yuzu\main.cpp:GMainWindow:275: yuzu Version: yuzu Development Build | master-0b9ef3c0-dirty
[   0.958095] Frontend <Info> yuzu\main.cpp:LogRuntimes:220: MSVC Compiler: 1931 Runtime: 14.32.31326.0

This is the "Double-click to add a new folder to the game list" message
that shows up when users first launch yuzu and is most likely never seen
again. Previously this message was not re-translated.

ui: Status bars dock button becomes DOCKED/HANDHELD button

UI: Translate hotkey labels in configuration

Update some files with Qt 5.15.2 best practices in mind

service: hid: Fix gesture regression

Follow-up fixes for NVFlinger rewrite (Part 3) 

core/debugger: fix asio write usage

core/debugger: fix crash due to incorrect lambda capture

Idea works as follows, while going fullscreen we compare the current window geometry with
available screens and ask for an intersection rectangle, we go fullscreen where most of
the window is located

GuessCurrentScreen could also potentially be used to see which screen
the window is on for dynamic DPI handling