FStar VS citra

I don't think something that specific exists. There are a very large number of formal methods tools, each with different specialties / domains.

For verification with proof assistants, [Software Foundations](https://softwarefoundations.cis.upenn.edu/) and [Concrete Semantics](http://concrete-semantics.org/) are both solid.

For verification via model checking, you can check out [Learn TLA+](https://learntla.com/), and the more theoretical [Specifying Systems](https://lamport.azurewebsites.net/tla/book-02-08-08.pdf).

For more theory, check out [Formal Reasoning About Programs](http://adam.chlipala.net/frap/).

And for general projects look at [F*](https://www.fstar-lang.org/) and [Dafny](https://dafny.org/).

Don't get me wrong, there are times when Microsoft got it right the first time that was technically far superior to their competitors. Windows IOCP was theoretically capable of doing C10K as far back in 1994-95 when there wasn't any hardware support yet and UNIX world was bickering over how to do asynchronous I/O. Years later POSIX came up with select which was a shoddy little shit in comparison. Linux caved in finally only as recently as 2019 and implemented io_uring. Microsoft research has contributed some very interesting things to computer science like Z3 SAT solver and in collaboration with INRIA made languages like F* and Low* for formal specification and verification. But all this dwarfs in comparison to all the harm they did.

Most of the proof assistants out there: Lean, Coq, Dafny, Isabelle, F*, Idris 2, and Agda. And the main concepts are dependent types, Homotopy Type Theory AKA HoTT, and Category Theory. Warning: HoTT and Category Theory are really dense, you're going to really need to research them.

F* is a dependently typed language that can be transpiled to idiomatic C via the KReMLin compiler. It’s very ML-ish to write and you can leave out some proofs. It also has the benefit of being used to write a formally verified TLS implementation that’s in wide use throughout industry.

As I said, dependent types attempt to solve this problem. F* is a language where you can express complex logic as a type. The catch is, these types are checked by an SMT solver. If the solver can satisfy the type checking, then great, and you move on. If it can’t, you have no idea why, and either have to guess or manually write the proof anyway. Contrast this with Standard ML which has a proof of the soundness of its type system.

So kind of like F*? https://www.fstar-lang.org/

F*

Nevermind that academia has come up with far safer ways to do a few things but social norms & inertia prevent their wider adoption (well okay, it also has a barrier to entry in the education required to use it but I don't think someone with the knowledge to meaningfully contribute to an OS kernel can be considered uneducated nor unable to learn).

Maybe that's a little off topic here, but if you like fixing bugs, i suspect you might also enjoy showing that there are no bugs at all. Check out languages like F* https://www.fstar-lang.org/ It's a proof-oriented programming language. You can use it to write code that has no bugs at all. And you once you're done, can convert F* to C or other languages.

Doesn't cover 3DS (Citra)

Another wonderful option is to play Nintendo 3DS games with the Citra emulator. They look incredible. I would go so far as to say that if you're a fan of the console then this is the best way to experience its games, even better than on the original hardware. Again use 3840x1200 @ 60 Hz and full SBS. In Emulation -> Configure... -> Graphics -> Stereoscopy set it to "Side by Side". Also increase the renderer internal resolution to as high as your PC can handle (I used "5x Native"). We'll also have to set the display layout for our resolution and aspect ratio. Unfortunately, this has to be done manually. Browse to %APPDATA%\Citra\config and edit qt-config.ini with this in the [display] section:

After some more research, I discovered that the Citra devs discovered and fixed this issue by allowing the Back button to open the in-emulation menu. This fix was added on Jan 22 2023. When I checked the version of Citra available on the Google Play Store on my phone, it was a very old version from May 2021, which is strange because viewing the same Play Store page on my computer shows it was updated in April 2023... maybe your Play Store version is also outdated? If so, the only solution I can think of would be to install the apk from the Citra Nightly github repo.

https://citra-emu.org/ A 3ds emulator!

You might want to consider compiling it on your Mac yourself, rather than trying to download a build, given the situation with MacOS transitioning to ARM. Beyond that, your question is related ton emulation, not ROMs specifically, so if you still need help, ask on related subreddits like r/EmulationOnMacOS and r/CitraEmulator.

https://citra-emu.org/ just typing the console + emulator on any search engine should give u the best option most of the time

I used the one here (you need a github account): https://github.com/citra-emu/citra/actions/runs/5078058438

There have been several recent changes merged for custom textures. Here is one of the pull requests for example: https://github.com/citra-emu/citra/pull/6452. The slow loading you're talking about was only an issue for me if preload custom textures was enabled.