HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
andreaferretti
linear-algebra
Nim2015–2016
andreaferretti / linear-algebra

linear-algebra

Linear algebra for Nim

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

What to know before exploring

What it is

Linear algebra for Nim

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 week3 dated mentions

Observed mentions: 2015-08-08 15:48:20 UTC to 2016-01-03 07:05:32 UTC. Weeks start Monday, UTC.

012015-08-03 00:00:00 UTC to 2015-08-10 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 32015-08-10 00:00:00 UTC to 2015-08-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-08-17 00:00:00 UTC to 2015-08-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-08-24 00:00:00 UTC to 2015-08-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-08-31 00:00:00 UTC to 2015-09-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-07 00:00:00 UTC to 2015-09-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-14 00:00:00 UTC to 2015-09-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-21 00:00:00 UTC to 2015-09-28 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-09-28 00:00:00 UTC to 2015-10-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-10-05 00:00:00 UTC to 2015-10-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-10-12 00:00:00 UTC to 2015-10-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsOct 122015-10-19 00:00:00 UTC to 2015-10-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-10-26 00:00:00 UTC to 2015-11-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-02 00:00:00 UTC to 2015-11-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-09 00:00:00 UTC to 2015-11-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-16 00:00:00 UTC to 2015-11-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-23 00:00:00 UTC to 2015-11-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-30 00:00:00 UTC to 2015-12-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-07 00:00:00 UTC to 2015-12-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-14 00:00:00 UTC to 2015-12-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-21 00:00:00 UTC to 2015-12-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-28 00:00:00 UTC to 2016-01-04 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 28

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
Aug 32015-08-03 00:00:00 UTC2015-08-10 00:00:00 UTC101
Aug 102015-08-10 00:00:00 UTC2015-08-17 00:00:00 UTC000
Aug 172015-08-17 00:00:00 UTC2015-08-24 00:00:00 UTC000
Aug 242015-08-24 00:00:00 UTC2015-08-31 00:00:00 UTC000
Aug 312015-08-31 00:00:00 UTC2015-09-07 00:00:00 UTC000
Sep 72015-09-07 00:00:00 UTC2015-09-14 00:00:00 UTC000
Sep 142015-09-14 00:00:00 UTC2015-09-21 00:00:00 UTC000
Sep 212015-09-21 00:00:00 UTC2015-09-28 00:00:00 UTC101
Sep 282015-09-28 00:00:00 UTC2015-10-05 00:00:00 UTC000
Oct 52015-10-05 00:00:00 UTC2015-10-12 00:00:00 UTC000
Oct 122015-10-12 00:00:00 UTC2015-10-19 00:00:00 UTC000
Oct 192015-10-19 00:00:00 UTC2015-10-26 00:00:00 UTC000
Oct 262015-10-26 00:00:00 UTC2015-11-02 00:00:00 UTC000
Nov 22015-11-02 00:00:00 UTC2015-11-09 00:00:00 UTC000
Nov 92015-11-09 00:00:00 UTC2015-11-16 00:00:00 UTC000
Nov 162015-11-16 00:00:00 UTC2015-11-23 00:00:00 UTC000
Nov 232015-11-23 00:00:00 UTC2015-11-30 00:00:00 UTC000
Nov 302015-11-30 00:00:00 UTC2015-12-07 00:00:00 UTC000
Dec 72015-12-07 00:00:00 UTC2015-12-14 00:00:00 UTC000
Dec 142015-12-14 00:00:00 UTC2015-12-21 00:00:00 UTC000
Dec 212015-12-21 00:00:00 UTC2015-12-28 00:00:00 UTC000
Dec 282015-12-28 00:00:00 UTC2016-01-04 00:00:00 UTC101

What Hacker News says

3 sources
Hi, the short answer is "Yes, but ...". Yes, Pymod's PyArrayObject can be created & accessed entirely in Nim; yes, its length (actually, shape) is specified at runtime; and yes, it can be resized after creation. However, Pymod's PyArrayObject is designed for maximum binary compatibility with Numpy. As such: 1. It uses Numpy's array creation functions (such as `createSimpleNew`), which in turn uses the Python runtime memory allocator. So at the very least, Pymod assumes you've linked against `-lpythonX.Y`. 2. It integrates with Python's GC rather than Nim's GC. (This is why it's passed around as `ptr PyArrayObject` rather than `ref PyArrayObject` -- it's untouchable by the Nim GC, but instead uses Python refcounts.) Of course, we do intend to extend Pymod to include a pure-Nim sibling for PyArrayObject, but it doesn't exist yet. If you
Read the rest
want a high-quality no-Python-dependency VLA in Nim right now, I'd recommend this library by Andrea Ferretti [ https://github.com/unicredit/linear-algebra ]. It can link against your system BLAS, in addition to offering GPU support using NVIDIA CUDA. Andrea is another member of the Nim community who does a lot of scientific computing: http://rnduja.github.io/2015/10/21/scientific-nim/
In Using D and std.ndslice as a Numpy Replacement
The problem with the Python ecosystem is that there exist a lot of libraries for scientific computation mostly incompatible with each other (blaze, numpy, numba, numexpr, dask...). Some of them try to reintroduce types in order to compile to native code, thereby losing the advantages of dynamic typing. In short, it is a mess, and everyone is trying to add on this because the existing ecosystem is big and the cost of rewriting everything is deemed too high, so people try to fix python limitations at the library level, sometimes making python more cumbersome to write tha a conventional statically typed language (I am looking at theano). I don't think that Lua is that much of an improvement, and I do not have big hopes for the JVM. The growing number of projects trying to improve the situation with value types, off-heap allocations and C com
Read the rest
patibility are a sign that the VM is not suitable for scientific computing and will not be much better for a while. I instead hope that Nim will take a leading role for scientific computation. It has an easy syntax and is flexible enough to write libraries such as numpy. At the same time it is fast and C compatibility is trivial. Of course, there is a library ecosystem to build, but I think that this is more doable than trying to work against the language itself. I am trying to start this effort with https://github.com/unicredit/linear-algebra but the road is very long and I hope it takes off. I cannot really comment on Julia as I do not know it welll enough
In Making Cython as easy as Python

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.