Skip to content

Instantly share code, notes, and snippets.

@Whateverable

Whateverable/result

Created December 6, 2021 11:03
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save Whateverable/74bfd8efde8e192e5d61fab0d7a1e767 to your computer and use it in GitHub Desktop.
Save Whateverable/74bfd8efde8e192e5d61fab0d7a1e767 to your computer and use it in GitHub Desktop.
Download ZIP
Whateverable
Raw
result
2021-12-05T21:43:37Z #moarvm <nine> jnthnwrthngtn I wonder: am I actually on the right track? So far we've coped by mostly ignoring the signed/unsigned distinction, just like a hardware CPU does. The only difference to the VM is that we're trying to throw appropriate errors for overruns. Is all the added complexity and volume worth that? Or should we maybe push those boundary checks to HLL instead?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment