eisl VS slimv

sasagawa888/eisl: ISLisp interpreter/compiler (github.com)

I'm trying to incorporate parallel computing into Easy-ISLisp using pthreads. Currently, the associative lists of local variables, stacks, and pointers are independent for each thread. However, I'm facing a conflict, and it's not functioning as expected. If anyone has any reference materials regarding parallel Lisp, I would greatly appreciate it if you could share them with me. sasagawa888/eisl: ISLisp interpreter/compiler (github.com)

I prefer dynamically typed Lisp because it's easy to write. However, when it comes to large-scale code, bugs tend to occur that are not apparent until execution. Mistakes often go unnoticed. So, I believe that type inference combines the convenience of dynamically typed languages with the reliability of statically typed languages. Easy-ISLisp includes a type inferencer. Give it a try. sasagawa888/eisl: ISLisp interpreter/compiler (github.com)

I have released Easy-ISLisp ver3.03. I have changed the default garbage collector to Concurrent Mark & Sweep (CMS). Please refer to the documentation "GBC.md" for information about the garbage collector. Give it a try! sasagawa888/eisl: ISLisp interpreter/compiler (github.com)

sasagawa888/eisl: ISLisp interpreter/compiler (github.com)

Parallel GC was experimentally introduced in version 3.01. Mark and sweep operations are parallelized using pthreads. While a simple code can be fast, its performance may vary depending on the data size. It's peculiar yet quite intriguing.https://github.com/sasagawa888/eisl

I use Vim with slimv, and have for years.

Maybe you should stick to one new thing at a time. Vim is more than capable of handling Common Lisp. Look at Slimv and Vlime for vim-style SLIME. Focus on CL first. You can come back to Doom / Emacs later.

Neovim works just fine. I use Neoterm to send-to-repl, here's what my config looks like. Your other options include vlime and slimv. I switched to neoterm because it's simple, explicit, and doesn't create unpredictable windows. Works for any other language just as well.

https://GitHub.com/jpalardy/vim-slime is a terrible SLIME to be honest! It is not even a SLIME. It just This does not look like SLIME. It just copies text from one text buffer and paste it to another Vim buffer which is probably running a REPL. "Probably" because who knows what the target buffer is running. vim-slime does not care. This is not Superior Lisp Interaction Mode for $EDITOR (SLIME) in any way.

vim-slime does not connect to any Swank server. It does not understanding Lisp s-expressions. It would happily copy any random text into any random REPL and call it job done! Lisp interaction mode is much much more than just copying and pasting text around. A superior lisp interaction mode gives you live debugging, handling conditions, inspecting variables, navigating the stack frames, ... Vim-slime cannot do anything like this because, well, it just copy-pastes stuff around. Vim-slime is a disingenious and misleading name for a project that is not SLIME.

If you really want to use Vim, do yourself a favor and use https://github.com/kovisoft/slimv and experience a true Lisp interaction mode.

Join me vim brother and don't settle for forcing yourself to use emacs while developing in CL when you don't have to! You even have two vim options! https://github.com/kovisoft/slimv and https://github.com/vlime/vlime with a great comparison of the two: https://susam.net/blog/lisp-in-vim.html

I've seen SLIMV recommended as a SLIME alternative for Vim. Like SLIME, SLIMV is a SWANK client.

I found Vlime to be more updated than slimv and give a smoother experience. With time I've switched to bare neoterm which I highly recommend. CL and lisps in general are designed with a text repl in mind, so this is the method that is guaranteed to work on every obscure CL distribution, and also transfer well to any other REPL-based languages.

If you are already familiar with vim you may want to use slimv

You need Parinfer. Several versions are available for Vim. It's easier to learn than Paredit and works better with Vim-style editing anyway. Lisp emphasizes interactivity with the REPL. It helps if you can send forms you're editing to the REPL for testing. Try something like slimv.