Forum for discussion about what unsafe code can and can't do
active 2025-03-28 → 2026-07-02 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 462 days from 2025-03-28 to 2026-07-02. Pushes: 4 total, peak 2 in a day. Pull requests: 6 total, peak 3 in a day. Issues: 39 total, peak 5 in a day. Comments: 223 total, peak 12 in a day. Stars: 28 total, peak 2 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| RalfJung | 96 | 4 | 3 | 74 |
| ia0 | 15 | 0 | 0 | 15 |
| joshlf | 12 | 0 | 0 | 8 |
| saethlin | 11 | 0 | 0 | 7 |
| CAD97 | 11 | 0 | 1 | 7 |
| maxdexh | 9 | 0 | 0 | 6 |
| rust-rfcbot | 7 | 0 | 0 | 1 |
| theemathas | 6 | 0 | 0 | 6 |
| VorpalBlade | 6 | 0 | 0 | 6 |
| DemiMarie | 5 | 0 | 0 | 5 |
| ais523 | 5 | 0 | 0 | 4 |
| Noratrieb | 5 | 0 | 1 | 4 |
| Manishearth | 4 | 0 | 0 | 3 |
| programmerjake | 3 | 0 | 0 | 3 |
| tmiasko | 3 | 0 | 0 | 3 |
| bjorn3 | 3 | 0 | 0 | 3 |
| chorman0773 | 3 | 0 | 0 | 3 |
| JoJoDeveloping | 3 | 0 | 1 | 2 |
| ChayimFriedman2 | 3 | 0 | 0 | 2 |
| Lokathor | 2 | 0 | 0 | 2 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#411ChayimFriedman22026-07-02 01:04How does MMIO memory fit into the memory model, and can reference point to it?
- Issue#615rust-rfcbot2026-06-16 03:10Opsem extension proposal: atomic volatile accesses
- Issue comment#614Amanieu2026-06-07 01:22Can we allow opportunistic in-place argument passing?
- Issue comment#613RalfJung2026-06-06 07:58Does `&raw const/mut $path` invalidate mutable references
- Issue comment#613RalfJung2026-06-04 06:09Does `&raw const/mut $path` invalidate mutable references
- Issue#414rust-rfcbot2026-05-04 12:06Should validity of a reference depend on the *contents* of memory in any way?
- Issue#414rust-rfcbot2026-05-04 12:06Should validity of a reference depend on the *contents* of memory in any way?
- Issue comment#606nikic2026-04-27 08:01What about: inbounds memory that segfaults on access?
- Issue comment#606RalfJung2026-04-27 06:18What about: inbounds memory that segfaults on access?
- Issue comment#84RalfJung2026-04-24 12:04What about: invalid not-used-again values? Is "validity on typed copy" enough?
- Issue comment#84RalfJung2026-04-24 06:41What about: invalid not-used-again values? Is "validity on typed copy" enough?
- Issue comment#345vrtgs2026-04-23 21:50What about: mixed-size atomic accesses
- Issue#580RalfJung2026-04-16 10:42How can mprotect be used soundly?
- Issue comment#607bjorn32026-03-31 10:31Best practices for sharing memory with untrusted parties
- Issue comment#607comex2026-03-30 05:21Best practices for sharing memory with untrusted parties
- Issue comment#414saethlin2026-03-24 02:55Should validity of a reference depend on the *contents* of memory in any way?
- Issue comment#414chorman07732026-03-24 02:42Should validity of a reference depend on the *contents* of memory in any way?
- Issue comment#414niluxv2026-03-22 12:27Should validity of a reference depend on the *contents* of memory in any way?
- Issue comment#414niluxv2026-03-22 11:37Should validity of a reference depend on the *contents* of memory in any way?
- Issue comment#84RalfJung2026-03-22 09:10What about: invalid not-used-again values? Is "validity on typed copy" enough?
- Issue comment#316VorpalBlade2026-03-22 00:02About "unleaking": what is the required pointer provenance in `dealloc`?
- Issue comment#414RalfJung2026-03-19 20:54Should validity of a reference depend on the *contents* of memory in any way?
- Issue comment#328theemathas2026-03-15 10:20Removing allocations is technically unsound in OOM (out-of-memory) situations
- Issue comment#604Manishearth2026-03-08 23:50How far does repr(transparent)'s transparentness stretch in repr(Rust).
- Issue comment#604programmerjake2026-03-08 19:41How far does repr(transparent)'s transparentness stretch in repr(Rust).
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 28 stars here means stars gained during the window, not the repo's star count.