Looks like I'm going for a fetch
native that does all the networky stuff and returns a response
object.
Pulling fields out of objects is easy enough on the C side (with a wrapper function that builds an ObjString, pushes it onto the stack, uses it as a key to a table, pops the string, and then returns), and I'm going to add a global Object
class to Lox that doesn't have any behaviour (and I'm very tempted to use {
as a prefix operator for an object literal).
I still need to do URL parsing somewhere, there's pros and cons to both C and Lox, but I'm going to need to do string functions sooner or later, and this is a good reason.