This is the best C successor I've seen! Why aren't you using it, /g/?
?) C successor with manual memory management, ironed out edge cases, new take on error handling (that resembles well written error handling in C), generics, compile time reflection/execution (macros?), import .h works directly, exporting to C works directly, nullable types etc.
http://ziglang.org
take off every zig
seems pointless
If people still talk about Zig in 10 years I might believe it.
so similar syntax to rust, wonder why they kept
fn name(args) -> type {
monstrosity, appreciate defer keyword (know any other than Go that has that?)
just use D with --betterC switch
>>62305051
>(know any other than Go that has that?)
Swift
const io = @import("std").io;
pub fn main() -> %void {
%%io.stdout.printf("Hello, world!\n");
}
> @import
> ->
> %%
The syntax is absolute horrible, even worse than ATS or sepples.
>>62305051
Also C++ with a little initial work. (keyword: scope guard)
>>62305138
>The syntax is absolute horrible
my first reaction too. This language looks like a bigger pain in the ass than C to write code in just because of the syntax-level complexity
>>62304701
C will always be the king
>>62305138
what is this abomination
>>62304701
People have been trying to design a successor to C ever since about 1980 and they've never done it. Mainly because they keep trying to pile in whatever the hot new thing for languages to have is, and the reason people use C these days is that they want a known quantity, not the latest meme.
>>62304701
Still waiting for JAI
>>62307425
/thread
or something else sane with the same metaprogramming facility
The successor to C is Python and C.
>>62304701
>62304701>>62306953 >>62307019 >>62307425This
Looks messy, prety much really shitty looking compared to C