Viewing profile — quasilyte

Does anyone know what data structure is that? I never seen anything like it, so I'm interested in learning how to call it. :)

Congrats with v1.0! I remember the times when it was called MangoDB. :D

You might be interested in https://github.com/mvdan/gogrep/issues/32#issuecomment-56866... When gogrep becomes more usable as a library, it would be easier to write such Go program…

Mostly because plugins support in Go is not ideal and it still requires compilation (in plugin mode). I believe Daniel Martí plans to make gogrep usable as a library, so it will be…

Features: * Custom linting rules without re-compilation. * Diagnostics are written in a declarative way. * Quickfix action support. * Powerful match filtering features, like expres…

Planning to use this secret weapon on the next Go contributors workshop in Russia. :)

I've contributed https://go-review.googlesource.com/c/go/+/117615 thanks to appendCombine check. :3

With minor Emacs Lisp compiler patch (addition of %return, %goto and %label intrinsics), it is now possible to output Lisp that is optimal. Possible implementation (about 20 lines …

I see three main approaches for the tasks projects like ecaml and goism try to solve: 1. Use a plugin system (ecaml) 2. Transcompile to a target language (gosim and emscripten-like…

It is technically possible, but optimal solution will require more than catch and throw (cl-lib uses them) Simple demonstration: https://pastebin.com/vXp0qPw3 Some S-expressions wi…

I love Emacs Lisp. Emacs has really good support for it which continues to improve over time. But.. I love more than one language (and more than one Lisp for sure). Will you try to…

You can call map/reduce/filter from Go code: `xs := lisp.Mapcar(f, ys)`. Mapconcat is already used inside runtime implementation: https://github.com/Quasilyte/goism/blob/master/src…

Currently, no. Hope I get your question right.. Name mangling scheme preserves fully qualified package path. All goism sources live inside GOPATH (1), so nothing stops us from impl…

The potential damage can be reduced. There can be a backend that generates Emacs Lisp code. Not necessary optimized or idiomatic, but it could be a good starting point for rewritin…

Some optimizations are easier in Go than in Emacs Lisp, hence the potential quality of produced bytecode can be higher. For big packages that can be implemented in Go naturally ( n…

It is possible to emit Emacs Lisp instead of bytecode/lapcode. This was the first code generator target actually. Easier to debug, simpler to trust (for the end user) and not that …

I used Emacs Lisp for scripting tasks like code and data generation. It is great to have an ability to evaluate form right inside the spot you want results to be inserted. This kin…