Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
etyp
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
etyp
8mo ago
To quote the very first paragraph of the bytecode interpreter section[1]: > The style of interpretation it uses—walking the AST directly—is good enough for some real-world uses, but leaves a lot to be desired for a general-purpose script
2.
▲
by
etyp
8mo ago
There is a chance that the title here was intentionally worded to answer a question people are likely to search for, then actually answer their concerns.
3.
▲
by
etyp
9mo ago
This is one of those natural consequences of "everything is an expression" languages that I really like! I like more explicit syntax like Zig's labelled blocks, but any of these are cool. Try this out, you can actually (techn
4.
▲
by
etyp
9mo ago
Yeah I only found day 2, hopefully day 1 will appear though: https://www.youtube.com/watch?v=ZLRngpdV6Qg (edited to not assume anything)
5.
▲
by
etyp
9mo ago
is ,AOE too far?
6.
▲
by
etyp
10mo ago
I read it as "this was a big news story which we care about. You may know it, but it is not the primary reason. Here is the primary reason."
7.
▲
by
etyp
1y ago
Random note since Godbolt was mentioned: It's also fun to hop on play.rust-lang.org and see what different IRs look like via the "..." next to "RUN." Just look at how simple the HIR is pretty simple for "Hello
8.
▲
by
etyp
1y ago
This goes to show how Zig's language design makes everything look nicer and simpler - the `errdefer` patterns in tests are super nice! I've debugged my Zig tests with simple print debugging (or try to narrow it down to a standalon
9.
▲
by
etyp
1y ago
Zeek is well known in "security" spaces, but not as much in "developer" spaces. It did get me a bit excited to see Zeek here until I realized it was unrelated, though :)
10.
▲
by
etyp
1y ago
Practically, it's all through this `type_traits` header that (often) end up in unreadable messes. It's all possible because of the catchy acronym SFINAE. It doesn't make much sense to me either, so I avoid it :) https:/
11.
▲
by
etyp
1y ago
The Real Book was pretty fundamental helping me learn jazz. I think a lot of jazz people look down on it (or those who need it), but I didn't really get deep enough to see that. There's a short video from Adam Neely that opened
12.
▲
by
etyp
2y ago
I really love that static analyzers are pushing in this direction! I loved writing Clippy lints and I think applying that "it's just code" with custom checks is a powerful idea. I worked on a static analysis product and the r
13.
▲
by
etyp
2y ago
I like how this is structured. When I read that inline types get copied-on-borrow I was pretty put off. Then since fields of inline types can't be assigned new values it seems a bit better, as long as you roughly know what's happe
14.
▲
by
etyp
2y ago
I've actually tried serializing languages into protobufs. The main reason was it made communication from X random programming language to Java in a consistent, structured way. Seems like it's just how they sent the IR from OCaml t
15.
▲
by
etyp
2y ago
I'm excited to see how that x86 backend is, I haven't tried it yet. It's definitely an interesting step for a new language to do on its own
16.
▲
by
etyp
2y ago
Seems reasonable enough, but why would it (allegedly) send environment variables back via a POST? Even if it's entirely in good faith, I'd rather some random package not have my `env` output..
17.
▲
by
etyp
2y ago
Nietzsche is a very interesting example since there is a very obvious shift in his philosophy from The Birth of Tragedy to, say, The Gay Science. I understand the argument that the style of writing noticeably changes, and I'd be okay a
18.
▲
by
etyp
2y ago
Safe programs extend beyond those that Rust's borrow checker accepts though. There is more than one way to make a program safe, not all of them would be valid Rust.
19.
▲
by
etyp
2y ago
I don't think the C++ standard can be held up like that. Many compilers simply ignore it (or ignored it, they're getting better about these things). It's not because there's an omission, it's because writing a compi
20.
▲
by
etyp
2y ago
Yeah, I've never really considered using a grammar like that for string processing like they suggest. And it's the first thing they show. Maybe I'm missing out and I just haven't had the tooling.