You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
1$\begingroup$ Thank you. So there's no mathematical inconsistency, programmatic errors that would appear in oop programming languages... I want to use Kotlin as the main language. $\endgroup$– Kid ACommented Feb 13 at 8:11
-
1$\begingroup$ The ads say Lean 4 is implemented in Lean 4, so what's up with that? $\endgroup$– Andrej BauerCommented Feb 13 at 9:34
-
$\begingroup$ @AndrejBauer Most of Lean 4 is implemented in Lean 4, including the language server, parser, elaborator, and tactics. See here.. The logical kernel is still in C++, as is the interpreter which runs non-compiled Lean code. (The compiler uses Lean 4 to compile to C as an intermediate language and then to byte code.) There is an alternate Lean 4 checker Lean4Lean written in pure Lean 4, which could be a kernel. It is slower but it’s in pure Lean so can in the future be proved correct which is exciting. $\endgroup$– Jason RuteCommented Feb 13 at 13:15
-
$\begingroup$ Also my understanding is that to build Lean 4 there is a bootstrap of Lean 4 written in C++ so that you can then build Lean 4 in the C++ implemented bootstrap of Lean 4. So in that sense you could also say Lean 4 is also written in C++. $\endgroup$– Jason RuteCommented Feb 13 at 13:24
-
1$\begingroup$ @KidA The only real "difficulty" is that object-oriented programs tend to be difficult to "reason about". Functional languages are far easier in this regard, which is probably one more reason why most proof assistants are written in functional languages. Jason Rute's answer gives more reasons why functional languages may be preferable. $\endgroup$– Alex NelsonCommented Feb 15 at 15:29
|
Show 1 more comment
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_`
- quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a> - MathJax equations
$\sin^2 \theta$
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. type-theory), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you