bflat

Strong replacement for Ocaml which is also performant and has rich ecosystem is F#. Technically speaking, Java and C# would serve somewhat different purposes and I would rather recommend Kotlin and C# with the former serving higher-level code goals better with existential types, SRTPs and overall strong type system and the latter for lower-level and/or performance-sensitive code with SIMD, pointers/byrefs, struct generics (zero-cost abstractions) and free/cheap interop. The only concern is how well Kotlin Native works today regarding compatibility. NativeAOT has seen a lot of work to improve this and scenarios that will never be supported (runtime reflection emit which needs JIT or arbitrary unbound reflection) are now well-documented. You may also be interested in Bflat[0] which has 'UEFI' as a target or even Zerosharp[1] as a demonstrat

I've been wondering how to integrate modern .NET Core into a custom build system (buck2) and was wondering similar things. There's this project I think is cool called bflat[1] that basically makes the C# compiler more like the Go compiler in the sense it's a one-shot single-use tool that can cross compile binaries natively. It's done by one of the people on the .NET Runtime team as a side project, and quite neat. I mostly use Visual Studio but I think in practice you're supposed to compile whole .dll's or assemblies all at once, which acts as the unit of compilation; I don't think the csharp compiler generates native object-files-for-every-.cs or translation unit, the kind of approach you'd expect from javac or g++. Someone please correct me if I'm wrong though! I'd like to learn more if there's a more granular/incremental unit of compila

It uses malloc in place of the GC’s allocator, so objects stay allocated forever: https://github.com/bflattened/bflat/blob/master/src/zerolib/...

It uses malloc in place of the GC’s allocator, so objects stay allocated forever: https://github.com/bflattened/bflat/blob/master/src/zerolib/...

I think it means that reference type objects stay allocated forever, but I'm not sure. From [0]: If an API allocates as part of its operation and doesn't return that as result, it's not good. We don't have a GC. This is all memory leaks. [0] https://github.com/bflattened/bflat/tree/master/src/zerolib

I'm having a hard time understanding how memory management works with the no-GC Zero stdlib. I see this but I don't get it. Anyone see a better explanation? https://github.com/bflattened/bflat/tree/master/src/zerolib

There's a GitHub issue about it: https://github.com/bflattened/bflat/issues/6

We changed the URL from https://github.com/bflattened/bflat to the project page. Both are nice, but the project page is more unique. Yes I know you can't be "more unique".