#macro_rules!

Right methodology, not nearly powerful enough

#proc_macros

Lisp-like methodology, but syn crate and DIY the AST, more importantly, the unholy diabolical compile times involved

#crabtime

idk, give reviews

Only if they learned from #Zig's #comptime/ #OCaml's #ppx

LET ME WRITE #RUST **AND** MANIPULATE ASTs, NOT AN XOR OF THEM

I've finally managed to tick off a box for my raylib bindings that I wanted to solve for literal years.

Like upstream raylib, we now separate the library into modules of `core`,
`text`, `shapes`, `textures`, `models`, and `audio`. The types all live
in `core`. This allows linking only a subset of the library surface, for
smaller binaries. A super-module `raylib` re-exports everything to link
the whole binding (including `rlgl`), so there is no breakage for users.

#ocaml #raylib

๐Ÿš€ Oh joy, another #language mashup! #Coalton combines all your favorite parts of #Haskell, #OCaml, and #Lisp to create... well, something nobody asked for. ๐Ÿ˜‚ Just what we needed: Common Lisp with a personality crisis. ๐Ÿค”
https://coalton-lang.github.io/ #mashup #programming #humor #HackerNews #ngated
The Coalton Programming Language

Coalton is an efficient, statically typed functional programming language that supercharges Common Lisp by taking great ideas from Haskell, Scheme, and OCaml. New! Coalton language manual. May 2025: Robert Smith's talk at ELS 2025.

The Coalton Programming Language

Coalton is an efficient, statically typed Lisp with ideas from Haskell and OCaml

https://coalton-lang.github.io/

#HackerNews #Coalton #Lisp #Haskell #OCaml #programming #language #development

The Coalton Programming Language

Coalton is an efficient, statically typed functional programming language that supercharges Common Lisp by taking great ideas from Haskell, Scheme, and OCaml. New! Coalton language manual. May 2025: Robert Smith's talk at ELS 2025.

The Coalton Programming Language

My first taste of Lean.

Numerical integration of the standard normal distribution - it feels more like a modern OCaml used as a general-purpose language.

#Lean #Ocaml ๐Ÿซ

OCaml Weekly News, for the week of May 19 to 26, 2026

https://discuss.tchncs.de/post/60986489

OCaml Weekly News, for the week of May 19 to 26, 2026 - tchncs

Lemmy

The #OCaml Weekly News for 2026-05-26 is out

https://alan.petitepomme.net/cwn/2026.05.26.html

OCaml Weekly News

I write #java for work, and #rust + #nushell at home. I will absolutely ramble about things I have no idea on :p

loves #reverseengineering and #binaries, will work on anything and everything low level. I love OS level shit, from the desktop ux to driver stability. I will absolutely ramble about #linux #arch and #nixos

I occasionally dabble with functional programming, and will totally not shut up about my #ocaml mmtk port.

As an aside, avid movie watcher, reader, manga enjoyer, anime enjoyer, and fanfic reader.

Here to have fun and enjoy!

We have another confirmed talk for the #FPIndia #Bangalore #meetup tomorrow! Ishaan will talk about Discrete optimisation and #MiniZinc! hasgeek.com/fpindia/bang... #Haskell #PureScript #Erlang #Scala #OCaml #Rust #Clojure

Bangalore FP May 2026 meetup
Bangalore FP May 2026 meetup

Bangalore FP May 2026 meetup

I intended to write this for a while: Security issues to look out for in OCaml (based on security issues I discovered or helped fix in the past): https://discuss.ocaml.org/t/security-issues-to-look-out-for-in-ocaml/18158
OCaml prevents a certain category of security issues, but that shouldn't make us over-confident.

I tried to generalize a bit:

* security properties don't compose: module A and B can be secure on their own, but you still need to test/fuzz their interaction

* Look at security bugs fixed in other ecosystems. Chances are the OCaml implementation fell into the same trap that other implementations did.

#ocaml #security

Security issues to look out for in OCaml

Continuing the discussion from Request for comments: What to do with opam packages that have known security vulnerabilities: That is mostly true, but it is worth keeping in mind that security issues can be present in any language and arenโ€™t limited to memory-safety. Trying to summarize the security issues that Iโ€™ve discovered or help fix: security properties donโ€™t compose: module A and B can be secure on their own, but you still need to test/fuzz their interaction. look at security bugs fix...

OCaml