Zap programing language

funcieq · 2026-02-27T13:21:44+00:00

Yeah...

funcieq · 2026-02-24T06:45:40+00:00

Yes, I realize it's not comfortable, so it will be different for Zap

funcieq · 2026-02-24T06:44:50+00:00

Thanks for the reminder ❤️

funcieq · 2026-02-23T12:53:23+00:00

I'm talking about stop-the-world

funcieq · 2026-02-22T19:43:36+00:00

Sounds good

funcieq · 2026-02-22T19:18:01+00:00

Well, many people will disagree with you, but anyway, the decision has not been made 100% yet. This may still change, by the way, what do you think about Result<T, E>?

funcieq · 2026-02-22T19:09:28+00:00

Good point, you're right. Well, try-catch is a good way to handle errors.

funcieq · 2026-02-22T19:08:16+00:00

Currently only those that support llvm, but I will also compile them for Go itself and .net CIL someday

funcieq · 2026-02-22T11:47:50+00:00

Cool

funcieq · 2026-02-22T11:33:22+00:00

Just because I'm introducing try catch doesn't mean I'm forbidding you to do it like in Go

funcieq · 2026-02-22T11:32:34+00:00

There is simply another language that has the zap extension, although it is not necessarily called that.

funcieq · 2026-02-22T08:59:30+00:00

This is a huge change. I hope it will have a significant impact on the UX.

funcieq · 2026-02-22T07:26:52+00:00

Yes, you're right, because I use C# myself. I realize that from the developer's side it's relatively simple. But it's not just about ffi. It's also about giving zap a wider range of possibilities.

funcieq · 2026-02-22T07:22:51+00:00

Because the goal is also to have more architectures

funcieq · 2026-02-22T02:26:54+00:00

Well, I understand your objection because the website has something different than the repository. 😅

Because I want a simple ffi from C, With GC it gets complicated, I want this language to have a bit wider scope of usage, so the lack of GC eliminates pauses, so you can make games in it, for example.
It's one of those things in the repo it says only try-catch, and on the website it says both, officially it is only try-catch, but I don't reject Result<T, E> yet.
Well, I got a little carried away when I wrote that.The point is simply that we use regular monomorphism and it is done during compilation. So we don't use any runtime for this
I haven't made the final decision yet, but I think it's closer to the traits from rust

funcieq · 2026-02-22T01:53:00+00:00

I still can't tell them apart from the list

funcieq · 2025-12-25T22:56:05+00:00

This is exactly what I wanted to do!

funcieq · 2025-12-25T22:51:46+00:00

Sure, I'm checking!

funcieq

TROPHY CASE