You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/decisions/0002-use-rust-for-core-engine.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,6 @@
1
1
# Use Rust for Core Engine Instead of C3
2
2
3
3
- Status: accepted
4
-
- Deciders: Development Team
5
-
- Date: 2024-12-19
6
4
7
5
Technical Story: The project needs a robust, modern, and maintainable language for its core logic to ensure long-term viability and developer productivity.
Copy file name to clipboardExpand all lines: docs/decisions/0003-avoid-async-for-simplicity.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,6 @@
1
1
# Avoid Async Rust for Core Engine Simplicity
2
2
3
3
- Status: accepted
4
-
- Deciders: Development Team
5
-
- Date: 2024-12-19
6
4
7
5
Technical Story: As we adopt Rust, we need to decide on a concurrency model that fits the project's goals of simplicity and performance for a CPU-bound workload.
Copy file name to clipboardExpand all lines: docs/decisions/0004-rust-native-collision-detection.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,6 @@
1
1
# Rust-Native Collision Detection for Ray Casting Performance
2
2
3
-
- Status: proposed
4
-
- Deciders: [Performance Analysis and Architecture Review]
5
-
- Date: 2025-07-27
3
+
- Status: accepted
6
4
7
5
Technical Story: Performance bottleneck identified in ray casting where JavaScript-based collision detection causes ~250ms per light update due to expensive WASM bridge calls.
0 commit comments