Eric Myhre
Eric Myhre
The stack traces produced by quicktest are extremely awesome. However, I've found a scenario where they can be verbose in a way that's probably a bug: inline function definitions. It's...
As @chafey has pointed out lately, the selectors specs could use more examples to make them easier to understand, and also give implementer more fixtures to work with. We have...
IPLD Schemas contain a couple of type definitions that are so useful that we don't want to repeat them in each schema. These are declared in something called the "prelude",...
I'm trying to implement a single-pass (no backtracking; no re-parsing or multipass hijinx) no-extraneous-allocations (I can do lookahead, but only if it's a fixed amount that's in no way data-dependent)...
A couple of todos to keep our docs up to date: - There's still a few places in the specs and docs prose that refers to "default", which we've long...
**background / current status** In IPLD Schemas, we already have the `keyed`, `kinded`, `envelope`, `inline`, and even `byteprefix` representations available for unions. Each of these representation strategies does something slightly...
Could IPLD Schemas include complex qualifiers and constraints, like regexps? Maybe! (Meta: This may spawn an exploration report or other docs, but I'm starting with an issue for now, as...
Hello! Spacemonkey errors are awesome! Using them in my projects has resulted in a huge reduction in boilerplate and grouping things into hierarchies has made my errors and handling much...
Porting schema fixtures from yaml to testmark format. Reviewing with a fine-tooth comb as I go, and interspersing documentation, since the format permits it. I'm aiming for a documentation level...
What ------- Roughly: ``` type JustFigureItOut union | | Hello # note no discriminant info here at all | World } representation probe # also no info type Hello struct...