HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ShivamSarodia
ShivyC
Python2018–2018
ShivamSarodia / ShivyC

ShivyC

C compiler created in Python.

4Distinct people
5Mentions
0Explicit recommenders
1.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

C compiler created in Python.

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, 5:04:57 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 day5 dated mentions

Observed mentions: 2018-03-30 20:43:44 UTC to 2018-04-24 19:15:27 UTC.

0122018-03-30 00:00:00 UTC to 2018-03-31 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsMar 302018-03-31 00:00:00 UTC to 2018-04-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2018-04-01 00:00:00 UTC to 2018-04-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-02 00:00:00 UTC to 2018-04-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-03 00:00:00 UTC to 2018-04-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-04 00:00:00 UTC to 2018-04-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-05 00:00:00 UTC to 2018-04-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-06 00:00:00 UTC to 2018-04-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-07 00:00:00 UTC to 2018-04-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-08 00:00:00 UTC to 2018-04-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-09 00:00:00 UTC to 2018-04-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-10 00:00:00 UTC to 2018-04-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-11 00:00:00 UTC to 2018-04-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 112018-04-12 00:00:00 UTC to 2018-04-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-13 00:00:00 UTC to 2018-04-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-14 00:00:00 UTC to 2018-04-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-15 00:00:00 UTC to 2018-04-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-16 00:00:00 UTC to 2018-04-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-17 00:00:00 UTC to 2018-04-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-18 00:00:00 UTC to 2018-04-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-19 00:00:00 UTC to 2018-04-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-20 00:00:00 UTC to 2018-04-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-21 00:00:00 UTC to 2018-04-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-22 00:00:00 UTC to 2018-04-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-23 00:00:00 UTC to 2018-04-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-24 00:00:00 UTC to 2018-04-25 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 24

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
Mar 302018-03-30 00:00:00 UTC2018-03-31 00:00:00 UTC211
Mar 312018-03-31 00:00:00 UTC2018-04-01 00:00:00 UTC202
Apr 12018-04-01 00:00:00 UTC2018-04-02 00:00:00 UTC000
Apr 22018-04-02 00:00:00 UTC2018-04-03 00:00:00 UTC000
Apr 32018-04-03 00:00:00 UTC2018-04-04 00:00:00 UTC000
Apr 42018-04-04 00:00:00 UTC2018-04-05 00:00:00 UTC000
Apr 52018-04-05 00:00:00 UTC2018-04-06 00:00:00 UTC000
Apr 62018-04-06 00:00:00 UTC2018-04-07 00:00:00 UTC000
Apr 72018-04-07 00:00:00 UTC2018-04-08 00:00:00 UTC000
Apr 82018-04-08 00:00:00 UTC2018-04-09 00:00:00 UTC000
Apr 92018-04-09 00:00:00 UTC2018-04-10 00:00:00 UTC000
Apr 102018-04-10 00:00:00 UTC2018-04-11 00:00:00 UTC000
Apr 112018-04-11 00:00:00 UTC2018-04-12 00:00:00 UTC000
Apr 122018-04-12 00:00:00 UTC2018-04-13 00:00:00 UTC000
Apr 132018-04-13 00:00:00 UTC2018-04-14 00:00:00 UTC000
Apr 142018-04-14 00:00:00 UTC2018-04-15 00:00:00 UTC000
Apr 152018-04-15 00:00:00 UTC2018-04-16 00:00:00 UTC000
Apr 162018-04-16 00:00:00 UTC2018-04-17 00:00:00 UTC000
Apr 172018-04-17 00:00:00 UTC2018-04-18 00:00:00 UTC000
Apr 182018-04-18 00:00:00 UTC2018-04-19 00:00:00 UTC000
Apr 192018-04-19 00:00:00 UTC2018-04-20 00:00:00 UTC000
Apr 202018-04-20 00:00:00 UTC2018-04-21 00:00:00 UTC000
Apr 212018-04-21 00:00:00 UTC2018-04-22 00:00:00 UTC000
Apr 222018-04-22 00:00:00 UTC2018-04-23 00:00:00 UTC000
Apr 232018-04-23 00:00:00 UTC2018-04-24 00:00:00 UTC000
Apr 242018-04-24 00:00:00 UTC2018-04-25 00:00:00 UTC101

What Hacker News says

5 sources
(self-promotion) I've created an open source C compiler written in Python (https://github.com/ShivamSarodia/ShivyC). I've learned a ton building it out so far, and I've found compiler design to be a great exercise in software engineering and learning Python since managing the complexity of a compiler is nontrivial. If you're interested in contributing, a good place to start is by tackling any of the issues marked as "good first issue".
In Ask HN: Python Open Source Projects for someone learning it after Java/Scala
The parser has a somewhat unusual structure: https://github.com/ShivamSarodia/ShivyC/blob/master/shivyc/p... It's been a while since I've had to use the phrase "exception-oriented programming", but it fits that code well. While that might be a useful or even necessary pattern to parse something like C++ which can have almost unbounded ambiguities, AFAIK C can be parsed solely by branching on the next token in the stream except for one tiny case (typedefs).
In Show HN: ShivyC – Hobby C compiler created in 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.