HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Ragnaroek
iron-wolf
Rust2026–2026
Ragnaroek / iron-wolf

iron-wolf

wolf3D in Rust

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

What to know before exploring

What it is

wolf3D in Rust

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

Observed mentions: 2026-02-21 15:52:20 UTC to 2026-02-22 03:15:47 UTC.

012026-02-21 15:00:00 UTC to 2026-02-21 16:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 21, 15:002026-02-21 16:00:00 UTC to 2026-02-21 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-21 17:00:00 UTC to 2026-02-21 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-21 18:00:00 UTC to 2026-02-21 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-21 19:00:00 UTC to 2026-02-21 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-21 20:00:00 UTC to 2026-02-21 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-02-21 21:00:00 UTC to 2026-02-21 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 21, 21:002026-02-21 22:00:00 UTC to 2026-02-21 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-21 23:00:00 UTC to 2026-02-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-22 00:00:00 UTC to 2026-02-22 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-22 01:00:00 UTC to 2026-02-22 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-22 02:00:00 UTC to 2026-02-22 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-22 03:00:00 UTC to 2026-02-22 04:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 22, 03: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
Feb 21, 15:002026-02-21 15:00:00 UTC2026-02-21 16:00:00 UTC110
Feb 21, 16:002026-02-21 16:00:00 UTC2026-02-21 17:00:00 UTC000
Feb 21, 17:002026-02-21 17:00:00 UTC2026-02-21 18:00:00 UTC000
Feb 21, 18:002026-02-21 18:00:00 UTC2026-02-21 19:00:00 UTC000
Feb 21, 19:002026-02-21 19:00:00 UTC2026-02-21 20:00:00 UTC000
Feb 21, 20:002026-02-21 20:00:00 UTC2026-02-21 21:00:00 UTC101
Feb 21, 21:002026-02-21 21:00:00 UTC2026-02-21 22:00:00 UTC000
Feb 21, 22:002026-02-21 22:00:00 UTC2026-02-21 23:00:00 UTC000
Feb 21, 23:002026-02-21 23:00:00 UTC2026-02-22 00:00:00 UTC000
Feb 22, 00:002026-02-22 00:00:00 UTC2026-02-22 01:00:00 UTC000
Feb 22, 01:002026-02-22 01:00:00 UTC2026-02-22 02:00:00 UTC000
Feb 22, 02:002026-02-22 02:00:00 UTC2026-02-22 03:00:00 UTC000
Feb 22, 03:002026-02-22 03:00:00 UTC2026-02-22 04:00:00 UTC101

What Hacker News says

3 sources
(equivalent C file: https://github.com/id-Software/wolf3d/blob/master/WOLFSRC/WL... ) > Was this translated automatically from C? I'll note that when I convert code between languages, I often go out of my way to minimize on-the-fly refactoring, instead relying on a much more mechanical, 1:1 style. The result might not be idiomatic in the target language, but the bugs tend to be a bit fewer and shallower, and it assists with debugging the unfamiliar code when there are bugs - careful side-by-side comparison will make the mistakes clear even when I don't actually yet grok what the code is doing. That's not to say that the code should be left in such a state permanently, but I'll note there's significantly more changes in function structure than I'd personally put into an initial C-to-Rust rewrite. The author of this rewrite appears to be t
Read the rest
aking a different approach, understanding the codebase in detail and porting it bit by bit, refactoring at least some along the way. Here's the commit that introduced that fn, doesn't look like automatic translation to me: https://github.com/Ragnaroek/iron-wolf/commit/9014fcd6eb7b10...
In Show HN: Iron-Wolf – Wolfenstein 3D source port in Rust
Was this translated automatically from C? I picked a spot totally at random and saw in https://github.com/Ragnaroek/iron-wolf/blob/main/src/act1.rs in place_item_type: let mut found_info = None; for info in &STAT_INFO { if info.kind == item_type { found_info = Some(info); break; } } When typically in rust this is just: let found_info = STAT_INFO.iter().find(|info| info.kind() == item_type); Now I want to go through and feng shui all the code to look more like idiomatic rust just to waste some time on a saturday...
In Show HN: Iron-Wolf – Wolfenstein 3D source port in Rust

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.