ra’s avatarra’s Twitter Archive—№ 37,826

      1. prototype of inline bytecode (cil*) in #jn. you have to report the type of the expression, and it is on you to balance the stack, but other than that it integrates nicely into the language (e.g. let bindings). next: nice names (e.g. add-ovf instead of Add-Ovf) and arguments
        oh my god twitter doesn’t include alt text from images in their APIoh my god twitter doesn’t include alt text from images in their API
        Permalink On twitter.com Twitter logo ra’s avatar ♻️ 1 Retweets ❤️ 9 Favorites Mood +3 🙂
    1. …in reply to @ra
      the hope is that cil* + staged compilation/generated functions + inlining can allow lower level parts of the language to be implemented in the language itself
      Permalink On twitter.com Twitter logo ra’s avatar ❤️ 2 Favorites Mood +3 🙂
  1. …in reply to @ra
    if youre careful and you know the compiler, you can totally cheat, like violating lexical scope! cil* is no joke
    oh my god twitter doesn’t include alt text from images in their APIoh my god twitter doesn’t include alt text from images in their API
    On twitter.com Twitter logo ra’s avatar ❤️ 4 Favorites Mood 0
    1. …in reply to @ra
      cil stands for common intermediate language, the official name for the clr's bytecode en.wikipedia.org/wiki/Common_Intermediate_Language
      Permalink On twitter.com Twitter logo ra’s avatar ❤️ 1 Favorite Mood 0
      1. …in reply to @ra
        woop woop, method and type references working!
        oh my god twitter doesn’t include alt text from images in their APIoh my god twitter doesn’t include alt text from images in their API
        Permalink On twitter.com Twitter logo ra’s avatar ❤️ 1 Favorite Mood 0
        1. …in reply to @ra
          s-expression bytecode side-by-side comparison
          oh my god twitter doesn’t include alt text from images in their APIoh my god twitter doesn’t include alt text from images in their API
          Permalink On twitter.com Twitter logo ra’s avatar Mood 0