Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
delphLonepaw
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
delphLonepaw
3y ago
LLVM just works well on the front that clang uses, after that, llvm itself is a wild beast full of worms, which is becoming more and more painful to work with if you are a language creator/mantainer, A lot of untested paths, and hidden
2.
▲
by
delphLonepaw
4y ago
I think the unused error is great, and a lot of people once they got used to it, it becomes quite the useful message, some bugs and some mistakes not easy to catch are quite there now. Giving it a bit of time is a good way to get used to it
3.
▲
by
delphLonepaw
5y ago
fun stuff, zig syntax error stuff is handled both by zls and zig fmt --ast-check (or if you care only for one file) zig ast-check =) For compile errors I think zig build is the only way
4.
▲
by
delphLonepaw
5y ago
it does not have it's own implementation of libc, it just makes easier to work with implementations of libc and letting the cross compile, I think it was like that. However a libc is a thing that zig probably wants and something I am
5.
▲
by
delphLonepaw
5y ago
That's a way of reading it
6.
▲
by
delphLonepaw
5y ago
I don't think a lot, I have no problems with UTF-8 strings (unless you speak in the source code, haven't tried), faster than c and rust when it can, ofc, I saw a rust program, made my own with zig, and it's fast , and I didn&
7.
▲
by
delphLonepaw
5y ago
Depends on the machine, on large projects, zig can take up to 10-15 seconds in my i5 12gb, ofc, after the first hit it becomes 0.01 recompiling without change (in case you removed the out and not the cache) and the first time you compile it
8.
▲
by
delphLonepaw
5y ago
Read the language reference, use ziglings, use ziglearn.org, use zls (don't trust it too much tho, but it will help a bit) and vscode or any text editor that supports jumping to the source, and of course, RTFS
9.
▲
by
delphLonepaw
5y ago
That's the language reference, that also links the experimental autogenerated std documentation Right now, Zig is young and the documentation is kinda ok (Language reference is clear enough, outside a few things that need better visibi