HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
BurntSushi
regex
Rust2017–2017
BurntSushi / regex

regex

Discover this repository through its Hacker News conversations.

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

What to know before exploring

What it is

A public description has not been verified.

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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:45:45 PM 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 hour2 dated mentions

Observed mentions: 2017-04-03 11:26:30 UTC to 2017-04-03 14:07:05 UTC.

012017-04-03 11:00:00 UTC to 2017-04-03 12:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 3, 11:002017-04-03 12:00:00 UTC to 2017-04-03 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 3, 12:002017-04-03 13:00:00 UTC to 2017-04-03 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-04-03 14:00:00 UTC to 2017-04-03 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 3, 14:00

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 3, 11:002017-04-03 11:00:00 UTC2017-04-03 12:00:00 UTC101
Apr 3, 12:002017-04-03 12:00:00 UTC2017-04-03 13:00:00 UTC000
Apr 3, 13:002017-04-03 13:00:00 UTC2017-04-03 14:00:00 UTC000
Apr 3, 14:002017-04-03 14:00:00 UTC2017-04-03 15:00:00 UTC101

What Hacker News says

1 sources
> If the search is guaranteed-linear-time in any case then why the requirement for a Turing-complete language? Because suggestions of using Turing-incomplete languages seem somewhat uninteresting to me. To be honest, I have never used one in anger, but if you told me to go write a production grade regex engine in Agda and Coq, I'd say you're nuts. It sounds like a fine experiment to do given infinite time, but I want people to actually use what I build. And I have a very strong suspicion that using one of those languages would take me 10 times as long to write it, if it's even possible at all. I try hard to blend the practical with the theory. I'm not aware of any Turing-incomplete language that comes close enough to the practical side of things. I hope that changes as PL research advances. :-) For the most part, my problem with your init
Read the rest
ial comment on the matter is that it neglects everything except for the "type system could have stopped it" part. But in reality, there are a host of trade offs at play given the actual choices available to me. (Even if those trade offs may be fundamentally orthogonal to the notion of type safety, they still exist and they are still things I must confront.) I feel like an Agda/Coq implementation would be dead in the water pretty quickly. How easy or hard is it to manipulate raw byte buffers in those languages? Or memory layout? That's why Rust is such a nice tool for a regex engine, because it gives you access to the hardware at the level of C without any fuss at all, while still remaining reasonably safe. A long time ago, we had a discussion about ASTs and property based testing. I noted that my "AST" couldn't be round-tripped with the concrete syntax accurately, and you noted that it was therefore not an AST. I'm in the middle of making that happen, and I've tried a bit harder this time around to use the type system to avoid invalid states. I do still have one that I haven't been able to rule out though, which is related to an invariant on a sequence of operations applied to a stack: https://github.com/BurntSushi/regex/blob/syntax-rewrite/rege...
In Fuzzing is magic – Or how I found a panic in Rust's regex library

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.