Re:Mathematical Notation, Past and Future (2000)
by kmill on Tuesday December 28, 2021 @11:28AM
(#29715164)
You might like Structure and Interpretation of Classical Mechanics by Sussman and Wisdom. It does classical mechanics using an MIT-Scheme library.
Lean/mathlib is a mix of functional programming and classical math notation. The community likes unicode quite a lot, with support by the editor (using quasi-Latex input methods in both VS Code and emacs). Here's an example from graph theory (I removed some conceptually irrelevant parts):
theorem simple_graph.sum_degrees_eq_twice_card_edges (G : simple_graph V) [fintype V] :
∑ (v : V), G.degree v = 2 * G.edge_finset.card
Re:Mathematical Notation, Past and Future (2000)
by kmill on Tuesday December 28, 2021 @01:34PM
(#29716443)
Speaking of which, there's a comment today about SICM in Clojure: https://news.ycombinator.com/item?id=29714267
Re:Mathematical Notation, Past and Future (2000)
by sidpatil on Tuesday December 28, 2021 @10:06AM
(#29714430)
Do you have a sample comparison between an expression/statement in math syntax versus in pseudocode syntax?
In short, a similar critique to that of Perl and PHP, except math is even worse.
Show me a Python-like notation for a math construct and I'm good to go. Even a Lisp!