joelreymont
Joined 18 years ago
Karma
273
Submissions
196
Member since
Jul 21
[ my public key: https://keybase.io/joelreymont; my proof: https://keybase.io/joelreymont/sigs/LggCRGdstZotd1x-FlJzj-M4ut-39swpjd9Wr8sB8ro ]
View on Hacker NewsRecent submissions
Comment · 10 months ago
Debugging Zig in LLDB is painful.
Slices show up as { ptr, len }, optionals are unreadable, and slice[0] just errors out. Python formatters help a bit but don’t fix expressions. zig-lldb fixes everything… if you’re willing to rebuild LLDB and maintain a fork.
zdb is a native LLDB plugin that sits in the middle:
- Works with stock LLDB (Homebrew / system) - Native C++ type summaries (no Python) - Zig-style expressions work: slice[0], opt.?, err catch x
(lldb) p int_slice[0] (int) $0 = 1
How? By calling LLDB’s internal APIs via versioned offset tables and rewriting expressions on the fly.
Limitations: no Variables View expansion (ABI issues with std::function). CLI debugging works great.
Check out the Github repo at https://github.com/joelreymont/zdb!
Comment · 11 months ago
Moving away from Github may end up killing the project.
Comment · 11 months ago
I'll gladly discuss at length things that are near and dear to my heart.
Facing random people in the public court of opinion is not one of them!
Also, there's long-form writing in my blog posts, Twitter and Reddit.
Comment · 11 months ago
Remind me please, when did I sign up to meet your expectations?
Comment · 11 months ago
With all due respect, try to read things before opining on them.
The PR explains why I did the work.
Comment · 11 months ago
It's both but the focus is on the future.
Comment · 11 months ago
I'm not trying to say that this is now projects ought to work right now.
I do think this is where we are heading, though.
No, existing open source projects are not ready for this and likely won't ever be.
It will start in the corporate world and maybe already has.
Comment · 11 months ago
Yep, that's me!
I will look into renaming myself, although don't think HN allows this.
Comment · 11 months ago
It was a bug in my own modes to the Zig compiler not in the stock compiler itself.
Comment · 11 months ago
This ought to be automated using AI.
It could first judge whether the PR is frivolous, then try to review it, then flag a human if necessary.
The problem is that Github, or whatever system hosts the process, should actively prevent projects from being DDOS-ed with PR reviews since using AI costs real money.
Comment · 11 months ago
This is an excerpt from the session where AI is writing my Lisp compiler. What do you call this? I call this doing what a competent developer does!
39/40 tests pass. The native reader works for integers, hexadecimal, lists, strings and quote forms. The one failure is symbol comparison (known limitation).
Based on the context summary and the user's note about cleanup, I should:
1. Continue Phase 3.5 self-compilation
2. Clean up the repo structure
Let me first update the todo list and then investigate the SIGKILL issue more
thoroughly. The issue is that combining reader source with file I/O code causes
the executable to be killed. Let me check if buffer-to-string with reader
works:
Let me test specifically reader + file I/O combined (which is what the
self-hosting test needs):Comment · 11 months ago
Are you speaking from experience?
Have you actually tried writing a "list" compiler?
Comment · 11 months ago
Check the 2nd PR, the one in my repo and not the one that was rejected.