Jesse Bouwman
Jesse Bouwman
Should we do this by adding an Allegro 11-specific base image? The version is parameterizable, but that doesn't work well with the existing CI matrix strategy.
> overly eager HTML escaping in Markdown code blocks also happens; example here: https://coalton-lang.github.io/reference/#quantizable-class This part has been fixed by #1166
> Sorry for the very slow response, things that touch this library tend to be scary so I tend to procrastinate. This looks quite reasonable, so I'll be sure to...
> Resolved conflicts. sparkles > > It seems [#215 (comment)](https://github.com/ipfs/go-ipfs-cmds/pull/215#discussion_r705179052) the only remaining question / concern – @jbouwman mind taking a look at @Stebalien's question? @lidel sure thing, done. @Stebalien...
> > does that look right, in terms of order of error checks? > > Yes. But I missed the other thing. I had cycles to look at this again....
> ok_hand nice > lgtm aside from the use of `'dag-jose'` over `dagJose.name` as mentioned inline Done -- thank you for the review. I arrived here after stepping through https://blog.ceramic.network/how-to-store-signed-and-encrypted-data-on-ipfs/...
hrefs contain an extra `coalton/` path component
Looks like the links are working now 🎊
@stylewarning @eliaslfox do you have guidance on this change?
Following up discussion with @stylewarning on 8/2, this changeset now places `lisp-toplevel` behind a `*features*` flag, for the time being, restricting usage to library source code until there is better...