Coq VS Steel Bank Common Lisp

Are those more important than, say: - Proven with Coq, a formal proof management system: https://coq.inria.fr/ See in the real world: https://aws.amazon.com/security/provable-security/ And check out Computer-Aided Verification (CAV). - Source: Hacker News / 6 months ago

Dafny and Whiley are two examples with explicit verification support. Idris and other dependently typed languages should all be rich enough to express the required predicate but might not necessarily be able to accept a reasonable implementation as proof. Isabelle, Lean, Coq, and other theorem provers definitely can express the capability but aren't going to churn out much in the way of executable programs;... - Source: Hacker News / 10 months ago

Still, there are many useful tools based on these ideas, used by programmers and mathematicians alike. What you describe sounds rather like Datalog (e.g. Soufflé Datalog), where you supply some rules and an initial fact, and the system repeatedly expands out the set of facts until nothing new can be derived. (This has to be finite, if you want to get anywhere.) In Prolog (e.g. SWI Prolog) you also supply a set of... Source: 10 months ago

Information about the Coq proof assistant: https://coq.inria.fr/ , https://en.wikipedia.org/wiki/Coq. Source: 12 months ago

This type of thing can help you formally verify code. So, if your proof is correct, and your description of the (language/CPU) is correct, you can prove the code does what you think it does. Formal proof systems are still growing up, though, and they are still pretty hard to use. See Coq for an introduction: https://coq.inria.fr/. - Source: Hacker News / 12 months ago

Tangential: if we're talking Lisp and native code speed, Steel Bank Common Lisp (by default) compiles everything to machine code. [0] https://sbcl.org. - Source: Hacker News / 7 months ago

Q5: Get http://sbcl.org/. Install https://quicklisp.org/. SBCL is the implementation that's the lowest friction, and Quicklisp is a package manager that's almost* painless. Source: 12 months ago

That is what we do in Lisp. Try sbcl if you haven't tried it yet. Source: about 1 year ago

I want to add the sbcl-doc subpackage (the manual for SBCL in GNU Info format), but first I need to understand how to write package definitions. As far as I understand there are the "templates" which are shell scripts that describe how a package is to be built and installed, and xbps-src is a shell script which can process these templates to actually carry out the work. Source: over 2 years ago

> Lisp looks like Python, that's far from C, and usually it's a "interpreted" language, far from machine the currently most popular Common Lisp implementation is based around an optimizing native code compiler. That compiler has its roots in the early 80s. See https://sbcl.org . It's far away from being 'interpreted'. - Source: Hacker News / almost 3 years ago