Developer note: Nearly every single one of my projects has started with these 3 thoughts:
That'd be cool.
It can't be that hard.
It should only take me a few hours to do.
Then I spend the next month* riding the Dunning Kruger wave - realising there's so much I don't know that I don't know! - and thinking my past self a fool for ever thinking this was possible.
Currently, with {c64asm}, you can compile 6502 assembly to machine code, incorporate data and text from R objects, and use calculations on R variables when compiling.
Once compiled to standard c64 program format (.prg), you can inject the program directly into a running VICE c64 emulator using {c64vice}.
The ultimate desired workflow is using RStudio as a c64 IDE.
{c64asm} is based on an older package of mind called {r64}, but it has been tidied up and simplified a bit.
{c64tass} used to reside within the {c64asm} package but was split off for the sake of simplicity.
{c64vice} is totally new and makes development faster as you can set memory and breakpoints in the machine much much easier than trying to do so from the command line.
Wait a minute. So there’s purrr and furrr. So furrr is purrr but in parallel? 🙀 Is this correct? Oh I am so going to learn more about furrr now! Also what’s up with those names? 😹😹😹
Vector index recycling is convenient but it would be really great if #rstats core could sort it so that it plays a sound effect of some chimes tinkling when it’s happening so I know to check I want that magic right now. Next R sprint maybe? ✨🧙♂️🪄