Agda VS zig

Most of the proof assistants out there: Lean, Coq, Dafny, Isabelle, F*, Idris 2, and Agda. And the main concepts are dependent types, Homotopy Type Theory AKA HoTT, and Category Theory. Warning: HoTT and Category Theory are really dense, you're going to really need to research them.

Does this come with plans to separately unify the body with each of the contexts induced by matching on each of the respective patterns (similar to what’s discussed here), or will it behave like the _ pattern and use only the most general context?

Coq, Agda, Lean, Isabelle, and probably some others which are not coming to my mind at the moment, but those would be considered the major ones.

Funny that you say this, because there are some obvious long standing open feature requests with looking up the type of the term under cursor — № 4295 and № 516. I am not blaming anyone in particular — this is the way it is. I wish I could find time to rewrite the proof search engine (how hard can it be), but I am already buried under a pile of other commitments and a good chunk of overwhelming sadness.

"Haskal is a mess, that's why I use a language that's written with Haskal."

Do it in Agda.

Agda is fun[1]. And there's also Idris[2] - more programming language, less proof assistant.

[1] https://wiki.portal.chalmers.se/agda/pmwiki.php https://github.com/agda/agda

At the most extreme level, you disappear into a meditative solitary retreat for a couple of years to seek enlightenment, and when you emerge you're no longer a programmer who writes programs, you're a theorist who proves theorems in Agda, and you have transcended above things that are tainted by the inherent evil of the material plane like "side effects" and "business needs" and "delivery timelines" and "could you stop doing that fancy math crap and just change the button's color like I asked for".

(For example, the standard dependent pair definition Σ, which is defined in Agda's core, does not have any).

It looks like the example is using the new multi-object for loop syntax, which was introduced after 0.10.1 was released.

looks like the project's now abandonned :

https://github.com/ziglang/zig/projects/2

This comment suggests otherwise:

https://github.com/ziglang/zig/issues/89#issuecomment-122118...

Although I'm not sure the "self hosted compiler" is the same as "llvm free backend".

#782 is the issue.

There's also a bug in Zig's translate-c, making awkward workarounds necessary for examples 42, 43 and 44 (described in README and in comments).

At one point, the Rust team switched away from the performant Jemalloc allocator to something more widely compatible (the system default). They chose to sacrifice performance in the sake of compatibility/stability. It's still available, but optional.

https://internals.rust-lang.org/t/jemalloc-was-just-removed-...

Insane performance gains, like the ones we see early in Zig, is something that can be easily eaten away by the natural evolution and maturity of a programming language.

Btw, Zig is beating trees with a stick to see what may fall down in this area: https://github.com/ziglang/zig/issues/12484

Zig, unlike C++ and Rust, doesn't need an optimized general purpose allocator in order to be fast. Zig outperforms its peers despite currently having a slow GPA in the standard library because the language encourages programmers down a path that avoids boxing the shit out of everything, which is inherently slow even if you have a global allocator optimized for this use case.

Rust switched away from Jemalloc because it uses global allocation for everything. Zig's convention of explicit allocator argument passing means such a compromise will never be needed.

As for "beating trees with a stick", I'll probably end up doing what I did for WebAssembly, which is to ignore the preexisting work and make my own thing that is better. Here's my 160-line wasm-only allocator that achieves the trifecta: high performance, tiny machine code size, and fundamentally simple.

https://github.com/ziglang/zig/blob/c1add1e19ea35b4d96fbab31...

Looks like squeek502 is working on a ".rc" to ".res" compiler: https://github.com/squeek502/resinator (plan is to upstream it to the Zig compiler at some point: https://github.com/ziglang/zig/issues/3702)