[image] Why did you learn OCaml? Or OCaml and Rust! Should make an amazing combo. Has anyone tried this and blogged about it? I haven’t delved into OCaml’s C interface enough to have much to say about this topic, and I’m just getting my feet wet in Rust. Rust is definitely the “spiritual offs…

[image] c-cube: Again, what “composable” system do you have in mind? NixOS? There are quite a few generic build systems out there. And for package managers (yes I think the two should be distinguished) Nix seems indeed to go into the right direction – wonderful PhD thesis, I recommend reading…

None of these package-managers (Nix, opam, cargo) that privilege the source, and assume as a default, that packages are built from source, are ever going to be suitable for production-systems use, except at the most boutique shops that can afford the sysadmin team to minister to them. For real prod…

[image] dbuenzli: Of course nobody is going to agree on a common system because every language specific community will want to be at the root of the dependency chain. Narrow minds. I think a lot of this is also a matter of how going viral affects programming language communities. Think of how…

It would be -much- more tractable if Dune were to generate (reasonably idiomatic) Makefiles, that were then used to execute the actual build. Then “composability” could be achieved at the level of those Makefiles. It would also allow a level of debuggability that is sorely lacking today. [yes, I r…

Why generate makefiles when you can generate ninja files? :slight_smile: I agree that if most major build tools were to export rules in such a low level builder, we could have better composability. In the meantime, I’ll keep considering cargo to be as nice as it gets for building and managing depen…

ninja files are meant only for -executing-. They’re not meant for reading, or writing by hand. the goal of “idiomatic” Makefiles is that it be easier to -glue- them together with other bits of Make. For instance, today if you find it painful-to-impossible to compiler your C++ code to binary using…

[image] bluddy: [image] Why did you learn OCaml? There is no way the C standard committee would do this kind of thing Strict aliasing was started by C, AFAIK, and it’s the ‘feature’ from hell. It literally made existing code crash in the most arbitrary manner costing me about a month of de…

[image] Chet_Murthy: None of these package-managers (Nix, opam, cargo) that privilege the source, and assume as a default, that packages are built from source Nix can be configured to look in a binary cache. That’s what Hydra and Cachix provide. The idea is you should never need to compile th…

As I wrote elsewhere, this isn’t enough. Package names and versions need to be human-readable and -writable. It is not sufficient that the source artifact has a human-readable name/version, because the binary artifact is the one that’s going to be installed. Also, I feel I must note again that I …

To your second point, I don’t see the difference. As I said, Nix cache can work for CI builds i.e. the builds that actually get deployed to production.

On interoperability between Rust and OCaml

Ecosystem

ninjaaron August 21, 2020, 12:38pm 35

And THAT’S why we all learned OCaml… because of something to do with Makefiles…

1 Like

Topic		Replies	Views
Cargo/Opam packaging of a Rust/OCaml project Ecosystem opam , ctypes , dune , bindings	22	3300	October 14, 2024
Advantages of OCaml over Rust Community	76	32739	September 4, 2019
Plans to choose an official package/project manager? Ecosystem	61	5825	October 28, 2021
The OCaml Platform - a vehement dissent Ecosystem build , dune	44	3321	September 20, 2023
Dependency hell makes it difficult to use OCaml for meaningful work Ecosystem opam	30	1075	March 19, 2026

On interoperability between Rust and OCaml

Related topics