Feature Request

What feature are you suggesting?

Overview:

Currently, the range list implementation performs linear search on the FindOverlaps method. The purpose of this method is finding all ranges that overlaps with the range that is passed as argument. This can be improved with the use of interval trees, a data structure designed for fast insertion, removal and lookup of int

As the complexity of the project grows, we find that often adding a change to QEMU configurations breaks something else unintended. This pretty much happens every single change and is becoming unmanageable. We need an actual test plan:

1. A set of .utm files of various operating systems, architectures, and configurations.
2. A checklist of things to test for each one (mouse, sound, network,

https://wiki.nesdev.com/w/index.php/Emulator_tests

It could run these ROMs and actually check the output somehow - perhaps either by checking memory values, or a copy of the screen buffer.

In Xenia, there are two kinds of declarations of kernel notification IDs:

• System notifications IDs are used simply as hard-written values, without any enum/consts/#defines, with merely comments indicating their original XN_SYS name.
• XAM apps (such as XmpApp) have notification IDs declared in their classes, as private static const uint32_t kMsg….

For future convenience especially when

It's nice if testing doesn't produce unnecessary artifacts after running with success but keeps relevant info on fail for further inspection.

Pytest should have a nice way of creating fixtures that can post-process a test based on whether it failed or not https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures

If a test fails, then keep the

A lot of files are missing copyright comments on the top.