HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
neeilan
neeilang
C++2020–2020
neeilan / neeilang

neeilang

Fast, type-safe, object-oriented language by yours truly

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

What to know before exploring

What it is

Fast, type-safe, object-oriented language by yours truly

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

Observed mentions: 2020-01-21 23:34:30 UTC to 2020-01-22 22:36:45 UTC.

0122020-01-21 23:00:00 UTC to 2020-01-22 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJan 21, 23:002020-01-22 00:00:00 UTC to 2020-01-22 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 01:00:00 UTC to 2020-01-22 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 02:00:00 UTC to 2020-01-22 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 03:00:00 UTC to 2020-01-22 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 04:00:00 UTC to 2020-01-22 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 05:00:00 UTC to 2020-01-22 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 06:00:00 UTC to 2020-01-22 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 07:00:00 UTC to 2020-01-22 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 08:00:00 UTC to 2020-01-22 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 09:00:00 UTC to 2020-01-22 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 10:00:00 UTC to 2020-01-22 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 22, 10:002020-01-22 11:00:00 UTC to 2020-01-22 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 12:00:00 UTC to 2020-01-22 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 13:00:00 UTC to 2020-01-22 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 14:00:00 UTC to 2020-01-22 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 15:00:00 UTC to 2020-01-22 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 16:00:00 UTC to 2020-01-22 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 17:00:00 UTC to 2020-01-22 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 18:00:00 UTC to 2020-01-22 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 19:00:00 UTC to 2020-01-22 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 20:00:00 UTC to 2020-01-22 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-22 21:00:00 UTC to 2020-01-22 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-22 22:00:00 UTC to 2020-01-22 23:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsJan 22, 22: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
Jan 21, 23:002020-01-21 23:00:00 UTC2020-01-22 00:00:00 UTC110
Jan 22, 00:002020-01-22 00:00:00 UTC2020-01-22 01:00:00 UTC000
Jan 22, 01:002020-01-22 01:00:00 UTC2020-01-22 02:00:00 UTC000
Jan 22, 02:002020-01-22 02:00:00 UTC2020-01-22 03:00:00 UTC000
Jan 22, 03:002020-01-22 03:00:00 UTC2020-01-22 04:00:00 UTC000
Jan 22, 04:002020-01-22 04:00:00 UTC2020-01-22 05:00:00 UTC000
Jan 22, 05:002020-01-22 05:00:00 UTC2020-01-22 06:00:00 UTC000
Jan 22, 06:002020-01-22 06:00:00 UTC2020-01-22 07:00:00 UTC000
Jan 22, 07:002020-01-22 07:00:00 UTC2020-01-22 08:00:00 UTC000
Jan 22, 08:002020-01-22 08:00:00 UTC2020-01-22 09:00:00 UTC000
Jan 22, 09:002020-01-22 09:00:00 UTC2020-01-22 10:00:00 UTC000
Jan 22, 10:002020-01-22 10:00:00 UTC2020-01-22 11:00:00 UTC000
Jan 22, 11:002020-01-22 11:00:00 UTC2020-01-22 12:00:00 UTC000
Jan 22, 12:002020-01-22 12:00:00 UTC2020-01-22 13:00:00 UTC000
Jan 22, 13:002020-01-22 13:00:00 UTC2020-01-22 14:00:00 UTC000
Jan 22, 14:002020-01-22 14:00:00 UTC2020-01-22 15:00:00 UTC000
Jan 22, 15:002020-01-22 15:00:00 UTC2020-01-22 16:00:00 UTC000
Jan 22, 16:002020-01-22 16:00:00 UTC2020-01-22 17:00:00 UTC000
Jan 22, 17:002020-01-22 17:00:00 UTC2020-01-22 18:00:00 UTC000
Jan 22, 18:002020-01-22 18:00:00 UTC2020-01-22 19:00:00 UTC000
Jan 22, 19:002020-01-22 19:00:00 UTC2020-01-22 20:00:00 UTC000
Jan 22, 20:002020-01-22 20:00:00 UTC2020-01-22 21:00:00 UTC101
Jan 22, 21:002020-01-22 21:00:00 UTC2020-01-22 22:00:00 UTC000
Jan 22, 22:002020-01-22 22:00:00 UTC2020-01-22 23:00:00 UTC202

What Hacker News says

4 sources
1) LLVM IR is strongly typed, which makes it very challenging to implement a dynamically-typed language on top of it. AFAIK, there aren't many (any?) successful such implementations of dynamically-typed languages. I haven't used other backend libraries, but I do think that looser typing at the IR level would make it a lot harder to catch implementation bugs; at least with LLVM, you are likely to hit an assertion if you break typing rules in the IR. 2) The type-checker is fairly ad-hoc, and I admittedly didn't look much into the literature here. The general idea is that since variable/function/class field types are explicitly typed, every expression can be checked for violating it's expected type. Implementation-wise, this is facilitated using the visitor pattern [1]. For certain expressions, some extra flexibility is allowed - for example
Read the rest
, assigning an object of a child class to a variable of the parent class is not a type error. [1] https://github.com/neeilan/neeilang/blob/master/src/type-che...
In Show HN: Neeilang: Minimalist OOP Language That Compiles to LLVM IR

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.