3 ms·
It's still… not the same. In CL (and specially with SBCL), we get compile time (type) errors and warnings at the blink of an eye, when we compile a single funct
by vindarel 3y ago
It's still… not the same. In CL (and specially with SBCL), we get compile time (type) errors and warnings at the blink of an eye, when we compile a single function with a keystroke (typically C-c C-c in Slime).
And there's also been improvement, see Coalton for a ML on top of CL. (https://github.com/coalton-lang/coalton/ https://github.com/coalton-lang/coalton/) (and SBCL itself evolves)
- housecarpenter 3y agoI haven't used CL myself, but it wouldn't surprise me if CL does a better job. Just pointing out that Python is significantly better in this respect than it used to be. In particular, using VS Code with Pylance, I can see type errors highlighted as soon as I write the code---I don't even need to use a keystroke. 24 years ago, I don't think anything like that was possible; the language didn't even support type annotations.
- llm_trw 3y agoIt's pretty much impossible to explain to people what it's like to work in a CL environment. A good presentation on what we're missing: https://www.youtube.com/watch?v=8Ab3ArE8W3s https://www.youtube.com/watch?v=8Ab3ArE8W3s
- zarathustreal 3y agoIf you’re part of the group missing something, how would you know?