agent281on Lobsters • Recommends
Data-Oriented Design Revisited: Type Safety in the Zig Compiler
0:00 / 0:00
#zigcompiler#typesafety#data-orienteddesign
Data-Oriented Design Revisited: Type Safety in the Zig Compiler - Matthew Lugg
Zig SHOWTIME
17K subscribers • 45 videos on Hallway
- Recommended by 1 person: 1 on Lobsters.
- Presented by Matthew Lugg, Zig compiler contributor
Advanced. Deep dive for people who know the field.
24K views2 years ago1 recommendation
Systems programmingProgramming languagesZigCompilers and interpretersData-oriented design
Matthew Lugg explains how the Zig compiler achieves type safety while adhering to data-oriented design principles for high performance.
From softwareyoucan.love Milan 2024 Intro Talk Q&AWhy it's here
1 person recommends thisWhat people say. Recommended for its deep dive into compiler internals and practical application of data-oriented design.
u/miyoyoin r/Zig • Mentions
On “Why not backticks for multiline strings?”
It being doable in one line doesn't mean it isn't possible in multiple.
The actual reason for strings being done this way is for general parsing/tokenization purposes, since every line can be parsed out of context, everything can be parallelized (and, in the example above, highlighted) without depending on anything else. This is why there are also no multiline comments.
A lot of decisions in Zig are taken specifically to make parts of, or the entire compiling process faster, and this is one of them. The following videos may give additional context:
[video
[video