News for hackers. Stuff that matters.
Re:RISC-V CPU formal specification F# edition by davidgrenier on Saturday July 29, 2023 @06:44AM (#36918866)
Re:RISC-V CPU formal specification F# edition by genter on Saturday July 29, 2023 @07:04AM (#36918995)
As far as F#/OCaml goes, that's excellent.

(I'm convinced one of the reasons why Rust is so popular is because it's OCaml with a legible syntax.)

Re:RISC-V CPU formal specification F# edition by pharmakom on Saturday July 29, 2023 @08:47AM (#36919757)
F# has diverged quite a lot from OCaml and is very readable IMO.

In any case, I think this view stems from our Algol/c/Java centric CS education system that casts ML and Lisp as weird and “unreadable”, when really it’s just a matter of perspective.

Re:RISC-V CPU formal specification F# edition by jcelerier on Saturday July 29, 2023 @09:33AM (#36920149)
> when really it’s just a matter of perspective.

it's really not, in the engineering school I did in the first year we were taught both C and LISP during the same semester and it was obvious to almost everyone except math nerds how much easier C was mapped to a normal human being (e.g. someone without prior programming experience)'s mental model of the world

Re:RISC-V CPU formal specification F# edition by yazzku on Saturday July 29, 2023 @11:12AM (#36921037)
Hadouken! They wish they had monads.
Re:RISC-V CPU formal specification F# edition by phillipcarter on Saturday July 29, 2023 @04:24PM (#36924183)
Not necessarily. I would say that the hand-rolled argument parsing business it a call for Argu: http://fsprojects.github.io/Argu/tutorial.html

But the code isn't all that complicated to begin with.