HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
def-
LPATHBench
C2014–2014
def- / LPATHBench

LPATHBench

Benchmarks of the longest path problem in various languages

Testing & Quality
Explore on GitHubRead Hacker News discussions
2Distinct people
3Mentions
0Explicit recommenders
3GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Benchmarks of the longest path problem in various languages

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, 1:49:46 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: 2014-12-20 21:43:35 UTC to 2014-12-30 16:16:02 UTC.

012014-12-20 00:00:00 UTC to 2014-12-21 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 202014-12-21 00:00:00 UTC to 2014-12-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-12-22 00:00:00 UTC to 2014-12-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-12-23 00:00:00 UTC to 2014-12-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-12-24 00:00:00 UTC to 2014-12-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-12-25 00:00:00 UTC to 2014-12-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 252014-12-26 00:00:00 UTC to 2014-12-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-12-27 00:00:00 UTC to 2014-12-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-12-28 00:00:00 UTC to 2014-12-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-12-29 00:00:00 UTC to 2014-12-30 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-12-30 00:00:00 UTC to 2014-12-31 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 30

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
Dec 202014-12-20 00:00:00 UTC2014-12-21 00:00:00 UTC101
Dec 212014-12-21 00:00:00 UTC2014-12-22 00:00:00 UTC000
Dec 222014-12-22 00:00:00 UTC2014-12-23 00:00:00 UTC000
Dec 232014-12-23 00:00:00 UTC2014-12-24 00:00:00 UTC000
Dec 242014-12-24 00:00:00 UTC2014-12-25 00:00:00 UTC000
Dec 252014-12-25 00:00:00 UTC2014-12-26 00:00:00 UTC000
Dec 262014-12-26 00:00:00 UTC2014-12-27 00:00:00 UTC000
Dec 272014-12-27 00:00:00 UTC2014-12-28 00:00:00 UTC000
Dec 282014-12-28 00:00:00 UTC2014-12-29 00:00:00 UTC000
Dec 292014-12-29 00:00:00 UTC2014-12-30 00:00:00 UTC101
Dec 302014-12-30 00:00:00 UTC2014-12-31 00:00:00 UTC101

What Hacker News says

3 sources
Cyther606·Dec 30, 2014
Nim is like writing C at the speed of Python, and running Python at the speed of C. If you took Python but made it perform blazingly fast, and made it suitable for the most demanding of embedded and systems programming applications, in addition to game dev, you'd get Nim. If on the other hand you're satisfied with Python, then keep using it. It was trivial for me to port a Python elliptic curve implementation to Nim. I'd certainly recommend it over Cython, because Nim is simply designed as one complete system built for writing high performance applications with a sane syntax. Statistics (on an x86_64 Intel Core2Quad Q9300): Lang Time [ms] Memory [KB] Compile Time [ms] Compressed Code [B] Nim 1400 1460 893 486 C++ 1478 2717 774
Read the rest
728 D 1518 2388 1614 669 Rust 1623 2632 6735 934 Java 1874 24428 812 778 OCaml 2384 4496 125 782 Go 3116 1664 596 618 Haskell 3329 5268 3002 1091 LuaJit 3857 2368 - 519 Lisp 8219 15876 1043 1007 Racket 8503 130284 24793 741 https://github.com/def-/LPATHBench/blob/master/nim.nim https://github.com/Araq/Nim/wiki/Nim-for-C-programmers
In Nim Advocacy and Promotion Strategies
Cyther606·Dec 29, 2014
https://github.com/def-/LPATHBench/blob/master/nim.nim Statistics (on an x86_64 Intel Core2Quad Q9300): Lang Time [ms] Memory [KB] Compile Time [ms] Compressed Code [B] Nim 1400 1460 893 486 C++ 1478 2717 774 728 D 1518 2388 1614 669 Rust 1623 2632 6735 934 Java 1874 24428 812 778 OCaml 2384 4496 125 782 Go 3116 1664 596 618 Haskell 3329 5268 3002 1091 LuaJit 3857 2368 -
Read the rest
519 Lisp 8219 15876 1043 1007 Racket 8503 130284 24793 741
In Nim (formerly Nimrod) 0.10.2 released
def-·Dec 20, 2014
I think the Nim code is also pretty readable: https://github.com/def-/LPATHBench/blob/master/nim.nim And Nim doesn't look bad in the other statistics (on an x86_64 Intel Core2Quad Q9300): Lang Time [ms] Memory [KB] Compile Time [ms] Compressed Code [B] Nim 1400 1460 893 486 C++ 1478 2717 774 728 D 1518 2388 1614 669 Rust 1623 2632 6735 934 Java 1874 24428 812 778 OCaml 2384 4496 125 782 Go 3116 1664 596 618 Haskell 3329 5268 3002
Read the rest
1091 LuaJit 3857 2368 - 519 Lisp 8219 15876 1043 1007 Racket 8503 130284 24793 741 Code size with gzip -9 < nim.nim | wc -c. Removed unused functions in Haskell.
In ARMv7 vs. x86-64: Pathfinding benchmark of C++, D, Go, Nim, Ocaml, and more

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.