summaryrefslogtreecommitdiff
path: root/src/core/memory.cpp
diff options
context:
space:
mode:
authorGravatar Lioncash2019-02-19 17:00:03 -0500
committerGravatar Lioncash2019-02-19 18:27:16 -0500
commit8d5d369b54f063606b7c21b2041c4d32154838d6 (patch)
treee33ff3d783d351e6d737e3554d3478630ce44af8 /src/core/memory.cpp
parentMerge pull request #2122 from ReinUsesLisp/vulkan-resource-manager (diff)
downloadyuzu-8d5d369b54f063606b7c21b2041c4d32154838d6.tar.gz
yuzu-8d5d369b54f063606b7c21b2041c4d32154838d6.tar.xz
yuzu-8d5d369b54f063606b7c21b2041c4d32154838d6.zip
service/nvflinger: Relocate definitions of Layer and Display to the vi service
These are more closely related to the vi service as opposed to the intermediary nvflinger. This also places them in their relevant subfolder, as future changes to these will likely result in subclassing to represent various displays and services, as they're done within the service itself on hardware. The reasoning for prefixing the display and layer source files is to avoid potential clashing if two files with the same name are compiled (e.g. if 'display.cpp/.h' or 'layer.cpp/.h' is added to another service at any point), which MSVC will actually warn against. This prevents that case from occurring. This also presently coverts the std::array introduced within f45c25aabacc70861723a7ca1096a677bd987487 back to a std::vector to allow the forward declaration of the Display type. Forward declaring a type within a std::vector is allowed since the introduction of N4510 (http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/n4510.html) by Zhihao Yuan.
Diffstat (limited to 'src/core/memory.cpp')
0 files changed, 0 insertions, 0 deletions