@whitequark@swetland really startling to find a situation where I'm like "this HTML page is so hard to read and navigate, I'll switch to the PDF ahh that's better"
@whitequark by the way, the block example, Katelyn G was saying there's some sort of unusual limitation on which basic blocks may follow each other, is there anything that stops me from br'ing between blocks?
I'm struggling with this week due to many issues that feel to me artificial. I don't like how this spec is written. I don't like a lot of the decisions
Buuut *sigh*
I guess I got the Good Idea out of the wasm spec I was hoping to find when I picked it. I was feeling like this S-expression form didn't "feel like" a LISP. And then I found this bit in the PDF spec. Using a syntax reordering trick to represent a Forth in LISP style. That's *saying this as if miserable* really smart actually
By the way if anyone has an easy way to point me to any of the following it would be much appreciated
- An example of the (block) syntax in textual wasm - An "alignment" is described in "memarg" in the spec, but this shows up nowhere in the textual wasm examples I find. Is this implicit in the use of `i32.` instructions? - Is there a way to query the current wasm stack depth?
@whitequark all right. if i'm trying to implement "putc" by pulling fd_write out of preview1 and telling it to print a single char from a single iov , am I to your knowledge missing a simpler method?
"JSON-LD" is short for "JavaScript Object Notation - LaserDisc" and refers simply to the standard JSON file format, stored on LaserDisc. JSON-LD was chosen for use in ActivityPub due to the many advantages of the LaserDisc format.
So. Creeping along with this. I am posting tihs from a bus.
Learned some more about "textual WASM". Two things I learned. One. It is LISP but also it is Forth. You write it as structurally an S-expression but the commands you write in that S-expression are, as it happens, instructions to a stack machine. This surprised me, but apparently Hotspot was a stack machine, as was the C# CLR as it was based on Hotspot, as is wasm because it was based on… Hotspot. Apparently this works well for JIT.
@dgoldsmith A note; when I enter the US, I fly into the US through Toronto Pearson airport, in which case you do customs clearance on the Pearson side. This places significant practical bounds on *how* badly customs can treat you.