Libretro 2.0 - RFC and announcement

[inactive123]

We have decided that starting as of RetroArch v1.1, a tentative spec called Libretro 2.0 will become the new spec.

The old spec will not be supported or updated/maintained after that. All libretro frontend implementations should upgrade to this new spec - to be finalized when RetroArch v1.1 hits.

I will list some of the things that will be addressed by libretro 2.0 in this issue tracker as we go along. We will try to only focus on the most bare essentials that we need to see addressed by libretro 2.0 so that we are future-proof for the next few foreseeable years.

I have tried to stave off having to break ABI for as long as possible, but in order to progress now, an ABI break is unavoidable.

[inactive123]

Some other things -

' unsigned num_roms;'

in the retro_subsystem_info_t struct - should be changed to something like 'num_content'. Avoid any and all usage of the terms 'roms' and 'emulator'. Substitute 'rom' for 'content' everywhere and 'emulator' should become 'core' or 'libretro core'.

Same thing here -

const struct retro_subsystem_rom_info *roms;

[Alcaro]

No comments on anything for about a week; I am going to assume implicit consent for most proposed changes. (I'll leave a few alone where the change doesn't seem to make much of a difference.)
If I'm being too eager here, we still have a few weeks to change things back. But we have to keep moving, or we'll blow the deadlines, and that won't make anyone happy.