HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Validark
Accelerated-Zig-Parser
Zig2025–2025
Validark / Accelerated-Zig-Parser

Accelerated-Zig-Parser

A high-throughput parser for the Zig programming language.

2Distinct people
2Mentions
0Explicit recommenders
284GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A high-throughput parser for the Zig programming language.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day2 dated mentions

Observed mentions: 2025-04-16 14:11:53 UTC to 2025-04-29 21:23:56 UTC.

012025-04-16 00:00:00 UTC to 2025-04-17 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsApr 162025-04-17 00:00:00 UTC to 2025-04-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-18 00:00:00 UTC to 2025-04-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-19 00:00:00 UTC to 2025-04-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-20 00:00:00 UTC to 2025-04-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-21 00:00:00 UTC to 2025-04-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-22 00:00:00 UTC to 2025-04-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 222025-04-23 00:00:00 UTC to 2025-04-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-24 00:00:00 UTC to 2025-04-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-25 00:00:00 UTC to 2025-04-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-26 00:00:00 UTC to 2025-04-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-27 00:00:00 UTC to 2025-04-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-28 00:00:00 UTC to 2025-04-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-29 00:00:00 UTC to 2025-04-30 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 29

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 162025-04-16 00:00:00 UTC2025-04-17 00:00:00 UTC110
Apr 172025-04-17 00:00:00 UTC2025-04-18 00:00:00 UTC000
Apr 182025-04-18 00:00:00 UTC2025-04-19 00:00:00 UTC000
Apr 192025-04-19 00:00:00 UTC2025-04-20 00:00:00 UTC000
Apr 202025-04-20 00:00:00 UTC2025-04-21 00:00:00 UTC000
Apr 212025-04-21 00:00:00 UTC2025-04-22 00:00:00 UTC000
Apr 222025-04-22 00:00:00 UTC2025-04-23 00:00:00 UTC000
Apr 232025-04-23 00:00:00 UTC2025-04-24 00:00:00 UTC000
Apr 242025-04-24 00:00:00 UTC2025-04-25 00:00:00 UTC000
Apr 252025-04-25 00:00:00 UTC2025-04-26 00:00:00 UTC000
Apr 262025-04-26 00:00:00 UTC2025-04-27 00:00:00 UTC000
Apr 272025-04-27 00:00:00 UTC2025-04-28 00:00:00 UTC000
Apr 282025-04-28 00:00:00 UTC2025-04-29 00:00:00 UTC000
Apr 292025-04-29 00:00:00 UTC2025-04-30 00:00:00 UTC101

What Hacker News says

2 sources
A lot of people have ways of accomplishing this, but my way is using compile-time execution in Zig (I know at least D, C++, and Terra have their own versions of this feature). You can specify a parameter as `comptime` and then do different things based on whatever conditions you want. You can also execute a lot of code at compile-time, including your sqrt check. E.g. I wrote a `pextComptime` function, which will compile to just a `pext` instruction on machines that have a fast implementation, otherwise it will try to figure out if it can use a few clever tricks to emit just a couple of instructions, but if those aren't applicable it will fallback on a naïve technique. https://github.com/Validark/Accelerated-Zig-Parser/blob/8782...
In Performance optimization is hard because it's fundamentally a brute-force task

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.