go

Building a Game Boy Advance emulator has gotten difficult, currently stuck on what appears to be I/O Registers not outputting their correct values and when a game is loaded in the gamepak, the device runs into a boot-loop. Investigating memory data and it’s meaning is difficult, converting binary data to something meaningful, then tracing that to another address if it’s a pointer and the cycle repeats. Doing these steps for every CPU cycle to investigate how data is changing is cumbersome and led to the project collecting dust for a few months as I gained the courage to dive into this....

Following discussions and read throughs on the following proposal, I hadn’t fully understood what the use case for this was or what the value of being able to range over functions would be. spec: add range over int, range over func · Issue #61405 · golang/go Following discussion on #56413, I propose to add two new types that a for-range statement can range over: integers and functions. In the spec, the table that begins the section would have a few mor…...