HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
teorth
estimates
JavaScript2025–2025
teorth / estimates

estimates

Code to automatically prove or verify estimates in analysis

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

What to know before exploring

What it is

Code to automatically prove or verify estimates in analysis

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, 3:56:07 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 day3 dated mentions

Observed mentions: 2025-05-02 10:27:42 UTC to 2025-05-10 17:23:35 UTC.

0122025-05-02 00:00:00 UTC to 2025-05-03 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsMay 22025-05-03 00:00:00 UTC to 2025-05-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-04 00:00:00 UTC to 2025-05-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-05 00:00:00 UTC to 2025-05-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-06 00:00:00 UTC to 2025-05-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 62025-05-07 00:00:00 UTC to 2025-05-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-08 00:00:00 UTC to 2025-05-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-09 00:00:00 UTC to 2025-05-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-10 00:00:00 UTC to 2025-05-11 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMay 10

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
May 22025-05-02 00:00:00 UTC2025-05-03 00:00:00 UTC202
May 32025-05-03 00:00:00 UTC2025-05-04 00:00:00 UTC000
May 42025-05-04 00:00:00 UTC2025-05-05 00:00:00 UTC000
May 52025-05-05 00:00:00 UTC2025-05-06 00:00:00 UTC000
May 62025-05-06 00:00:00 UTC2025-05-07 00:00:00 UTC000
May 72025-05-07 00:00:00 UTC2025-05-08 00:00:00 UTC000
May 82025-05-08 00:00:00 UTC2025-05-09 00:00:00 UTC000
May 92025-05-09 00:00:00 UTC2025-05-10 00:00:00 UTC000
May 102025-05-10 00:00:00 UTC2025-05-11 00:00:00 UTC110

What Hacker News says

3 sources
A defensive programming nit is not to return the desired result [1] but to show all collected cases are true. def defensive_true(): # assume False ... return arr.all(True) There are tests, but some wild refactoring in the night and "tests still pass," leading to a blind ship, could be a tiny risk. Not a big deal, just I don't trust myself to return the happy path if the middle could change. [1] https://github.com/teorth/estimates/blob/main/src/estimates....
In A proof of concept tool to verify estimates

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.