Isn't the Lean programming language a pure functional programming language? But surely much of the CPython C code is not written in a pure functional style. So the translation must not be trivial. How do they do it?
In their example, the CPython function get_len_of_range is a pure function, and the translation is trivial, as expected.
It would be helpful to show us a CPython function which is not purely functional, and its (presumably less trivial) translation.
I see they don't have complete coverage yet. Did they cherry-pick the functional parts of CPython to get started?
Yes put you can prove non-pure imperial language correct in LEAN. Understanding why takes a lot of learning unfortunately and can’t easily be summarised in a single answer. seL4 (for example) is a real-world-used-in-production kernel proven correct in a pure language (Isabel/HOL).
Aalesund, Norway [1,2] is another town with a lot of Art Nouveau buildings, not mentioned in the article. Much of the town burned down in 1904, and then some buildings were rebuilt in what they called Jugendstil style.
This misspelled boasting HN post title contrasts with the writing
in the detailed, thorough github README and docs directory
contents. Also the name of the HN poster does not resemble
the name on on the github repo ... ?
There is nothing in the repo that says it was made with AI, and there are none of the usual AI .md files. The amount, quality, and organization of
documentation is much better than in most quickie AI projects.
A completely different explanation, which I think is the right one:
I always thought the Macintosh menu bar was copied from UCSD Pascal[1], an alternative operating system that ran on Apple II computers in the 1970s and early 1980s. Bill Atkinson was said to be familiar with it.
A machine running UCSD Pascal always had a menu running across the top of the screen, and the contents of the menu changed with the application -- just like the Lisa and the Macintosh -- which came years later. The menu was accessed from the keyboard. UCSD Pascal did not support a mouse, and the Apple II did not have one.
Reproducing these binaries does not require a compiler, assembler, linker, libc, package manager, or language runtime. Prompt2ELF still depends on an x86-64 processor, the Linux syscall ABI, the kernel's ELF loader, and a filesystem. The machine has not disappeared. The conventional source-to-binary toolchain has. ...
The longer-term direction is a small multicall executable, similar in spirit to BusyBox, generated directly from prompts and Linux syscalls."
Most people programmed the IBM 1620 like in the rzzzwilson comment here: FORTRAN on punch cards, running out of reach in a closed machine room. But the 1620 did have a console terminal so it could be used interactively.
Somebody at IBM built an interactive APL interpreter that ran on the 1620, but it seems this was never released:
I'll be that guy who points out Pascal is the name of a once very popular programming language. Its heyday was the late 20th century, but it is still in use here and there. Confusion seems likely.
Is there any connection between this product and the Pascal programming language?
reply