News for hackers. Stuff that matters.
Re:Creating a Common Lisp implementation, part 1 [video] by drmeister on Tuesday August 25, 2020 @09:38PM (#24278172)
I can testify to a lot of the difficulties Robert Strandh talks about here. We implemented a Common Lisp in C++ that interoperates with C++ (https://github.com/clasp-developers/clasp.git). I ended up implementing a lot more C++ code than I wanted to and then replacing much of it with Common Lisp versions (during startup) because it's easier to maintain and we can use type inference to improve the performance of Common Lisp code while C++ code is 'stuck' with the types you compile it with. Bootstrapping is hard.
Re:Creating a Common Lisp implementation, part 1 [video] by dleslie on Tuesday August 25, 2020 @10:53PM (#24278599)
I like what you're doing, but I really wish you'd provide debs and rpms for x86 and arm; I use common lisp on machines with very little ram, and compiling is too much of a hassle. FWIW, ecl and sbcl are my go-tos.
Re:Creating a Common Lisp implementation, part 1 [video] by fiddlerwoaroof on Tuesday August 25, 2020 @11:24PM (#24278782)
I second this: making it easy for users to use your language implementation is very valuable. I routinely test my Lisp on every implementation I can reliably get my hands on, and I’ve never been able to build a good binary for clasp.
Re:Creating a Common Lisp implementation, part 1 [video] by stevelosh on Wednesday August 26, 2020 @11:47AM (#24283524)
Thirded. I would also add Clasp to my projects' list of implementations to run unit tests on[1] if I could easily install it on Ubuntu with a .deb.

[1]: e.g. adding a test-clasp clause to https://github.com/sjl/cl-digraph/blob/master/Makefile#L14-L...

Re:Creating a Common Lisp implementation, part 1 [video] by phoe-krk on Wednesday August 26, 2020 @12:23PM (#24283974)
> if I could easily install it on Ubuntu with a .deb.

Or even via Roswell - if that is even remotely possible.

Re:Creating a Common Lisp implementation, part 1 [video] by stevelosh on Wednesday August 26, 2020 @03:49PM (#24286487)
I don't use/like Roswell, so I'd really prefer a .deb if at all possible.
Re:Creating a Common Lisp implementation, part 1 [video] by dleslie on Thursday August 27, 2020 @02:18PM (#24296756)
Clasp is supplied via Roswell but fails to compile on Arm64.
Re:Creating a Common Lisp implementation, part 1 [video] by drmeister on Wednesday August 26, 2020 @12:54AM (#24279246)
Thank you. So debs for debian? I have great collaborators working with me now that could do this. We have one for Arch I believe. I just haven't prioritized this yet.
Re:Creating a Common Lisp implementation, part 1 [video] by dleslie on Wednesday August 26, 2020 @01:34AM (#24279456)
Debian and its derivatives, yes; I do most of my lisp from raspbian these days, but it's Debian compatible.
Re:Creating a Common Lisp implementation, part 1 [video] by Insanity on Wednesday August 26, 2020 @09:26AM (#24282237)
Cool, I'm curious, what do you do with lisp if you can share it?
Re:Creating a Common Lisp implementation, part 1 [video] by phoe-krk on Wednesday August 26, 2020 @12:22PM (#24283965)
Is that a general question, or a precise one?

In case it's the former, I have a ton of personal projects and small libraries in it, plus wrote a book on it that will get published by Apress[0].

[0] https://news.ycombinator.com/item?id=23843525

Re:Creating a Common Lisp implementation, part 1 [video] by Insanity on Wednesday August 26, 2020 @04:28PM (#24286901)
It was a precise one, but thanks! :D
Re:Creating a Common Lisp implementation, part 1 [video] by dleslie on Thursday August 27, 2020 @02:17PM (#24296749)
Tools for work, small web services that I share with friends, basically all my personal programming.
Re:Creating a Common Lisp implementation, part 1 [video] by zshrdlu on Wednesday August 26, 2020 @02:07PM (#24285313)
If you take the packaging route, cross-distribution packages like guix and nix would probably be best.
Re:Creating a Common Lisp implementation, part 1 [video] by betterunix2 on Tuesday August 25, 2020 @09:52PM (#24278248)
"we can use type inference"

Technically you cannot use type inference in Common Lisp, only in a subset of the language. This is not hard to prove: you can embed a language for which general type inference is impossible (i.e. for which some expressions must have explicit type annotations), like System F, in Common Lisp. One of my complaints about Common Lisp is that the type system is really annoying when you have complex types.

Re:Creating a Common Lisp implementation, part 1 [video] by reikonomusha on Tuesday August 25, 2020 @10:48PM (#24278577)
> One of my complaints...

Then build a language and type system atop, like with Coalton [0]. Lisp is for language building. Even Hindley-Milner was first implemented atop Lisp in 1973 [1].

[0] https://github.com/stylewarning/coalton

[1] http://www-public.imtbs-tsp.eu/~gibson/Teaching/CSC4504/Read...

Re:Creating a Common Lisp implementation, part 1 [video] by aidenn0 on Tuesday August 25, 2020 @10:33PM (#24278501)
Type inference isn't all-or-nothing. If you can infer even one type in one block of code, you can generate more efficient code.