llvm-pretty-bc-parser VS opendylan

Interestingly llvm-hs seems to have gotten a new maintainer which has ambitious ideas like using it for GHC and absorbing the bytecode parser llvm-pretty-bc-parser.

It's actually interesting how many independent implementations of bitcode writers there, given that there are almost no independent bitcode readers (mine is very preliminary, and then there's one from Galois[1]).

I believe Swift also does their own serialization in LLVM's bitstream format[2]. I also saw an implementation of the writer in Swift, but now I've lost it.

[1]: https://github.com/GaloisInc/llvm-pretty-bc-parser

[2]: https://github.com/apple/swift/blob/main/docs/Serialization....

Yes those were inspired by deuce, here is open dylan's version: https://github.com/dylan-lang/opendylan/tree/master/sources/...

Dylan, which was originally created by Apple: https://opendylan.org/

OpenDylan kept being developed for a long time even after Apple lost interest, and they still do releases every once in a blue moon, but the community is tiny, and nobody is doing anything with Dylan (save for the compiler itself).

what is this fairly close resemblance? Parentheses?

There are a bunch of Lisp like languages without s-expression syntax: Lisp 2, Logo, MDL, RLISP, CLISP (not the CL implementation), Dylan, Racket with its new syntax (Racket2, Rhombus), Skill, ...

For example Dylan is based on Scheme & CLOS + a different syntax + some other influences. https://opendylan.org

https://github.com/dylan-lang/opendylan/blob/master/sources/...

If they go with another language, it had damn well better be Dylan. Apple already designed it and screwed up when they abandoned it back then (circa Java).

Carp, Lux and Dale are 3 I'm familiar with.There's also Dylan, though that one dropped its parentheses. But if we go by the brackets, technically, we can argue that any expression-based languages is a Lisp. I once wrote a Lisp to JS transpile whose output had more parens than the input. :)