HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
checkedc
checkedc-clang
C++2016–2022
checkedc / checkedc-clang

checkedc-clang

This repo contains a version of clang that is being modified to support Checked C. Checked C is an extension to C that lets programmers write C code that is guaranteed by the compiler to be type-safe.

5Distinct people
5Mentions
0Explicit recommenders
516GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

This repo contains a version of clang that is being modified to support Checked C. Checked C is an extension to C that lets programmers write C code that is guaranteed by the compiler to be type-safe.

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

Observed mentions: 2016-06-14 08:16:38 UTC to 2022-02-13 15:51:30 UTC.

012016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022

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
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101

What Hacker News says

5 sources
Interesting. The important development is the porting tool which automatically infers the size of objects. Many people, including me [1], have proposed safer variants of C. The problem is converting legacy code. They've made some progress, but not enough to use yet. The important result is in Table 1 of the actual paper.[2] The converter looks at pointers, and classifies them as "pointer", "array of known size", or "unknown". "Unknown" ranges from 49% to 76%. You can't convert an existing code base automatically with that low a success rate. The big design mistake in C was "pointer" and "array" being the same thing syntactically. Trying to undo that has taken decades. Their converter is on Github.[3] This is a Microsoft project. The syntax they use is rather clunky: void copy(char ∗dst : bytecount(n), const char ∗src : b
Read the rest
ytecount(n), size_t n); That's halfway between C and Pascal/Ada/Rust. I proposed more C-like syntax like this: void copy(size_t n, char (&a)[n], const char (&b)[n]) It's annoying that you need the parentheses, but that's C/C++ syntax. I wanted to put C++ style references into C so you could pass arrays as arrays, rather than degrading them to pointers. I also wanted to add slices of arrays, so you could pass a slice of an array as an array. Those are standard features of most later languages, and handle most of the cases for which pointer arithmetic is used. C doesn't have the expressive power to even talk about those things unambiguously. So they can't be checked either at compile time or run time. The hard job is converting legacy code by automatically inferring the information that C source code lacks. It's good that they're trying. But a 50% success rate indicates they're just getting the easy hits. If anybody ever gets a good array size inference system, it would be a huge win. Then existing C could be converted to something better. Not necessarily "Checked C". Rust or Go would be options. [1] http://www.animats.com/papers/languages/safearraysforc43.pdf [2] http://www.cs.umd.edu/~mwh/papers/checkedc-incr.pdf [3] https://github.com/Microsoft/checkedc-clang
In Achieving Safety Incrementally with Checked C

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.