How I Built Zig-SQLite

Re:How I Built Zig-SQLite by akira2501 on Friday May 27, 2022 @01:59PM (#31532667)

I'm not wild about the new trend of languages of making a bunch of syntax dependent on a single small sigil. It gives me a strong feeling of Perl's historical "eclecticness" and I feel like I'm putting more effort into correctly reading the program back into my mind than I should ideally have to.

[ Parent | on HN ]

Re:How I Built Zig-SQLite by kzrdude on Friday May 27, 2022 @03:39PM (#31533946)

I'm wondering what the point of the period is here, could it be done without it?

[ Parent | on HN ]

Re:How I Built Zig-SQLite by throwawaymaths on Friday May 27, 2022 @08:32PM (#31536487)

I think it allows the parser to be context-free since otherwise it is tricky to distinguish it from a code block. They could have picked a different sigil, but I think . was landed on because it had the fewest semantic conflicts with other concepts in the language (for example % is used to denote modular arithmetic)

[ Parent | on HN ]

Re:How I Built Zig-SQLite by alpaca128 on Friday May 27, 2022 @04:14PM (#31534364)

I don't know why, but this is a part of the language's syntax, for example when matching a union type each named variant also has that period. Same with the argument for print statements (`print("{s}", .{var})`).

[ Parent | on HN ]

Re:How I Built Zig-SQLite by kzrdude on Friday May 27, 2022 @04:21PM (#31534442)

aha, seems like they use the list argument to print instead of having varargs functions then?

[ Parent | on HN ]

Re:How I Built Zig-SQLite by bo0O0od on Friday May 27, 2022 @10:32PM (#31537097)

In zig code blocks are expressions and can appear in a lot of places, e.g. on the RHS of an assignment. Probably possible to not need the dot but considerably more complicated.

[ Parent | on HN ]