https://github.com/64kramsystem/ray_tracer_challenge-completed

Implementation of the "Ray Tracer Challenge" in Rust, with additional parallelism
https://github.com/64kramsystem/ray_tracer_challenge-completed

concurrent-programming parallel-programming pragprog raytracing rust rust-lang

Last synced: 4 months ago
JSON representation

Implementation of the "Ray Tracer Challenge" in Rust, with additional parallelism

Host: GitHub
URL: https://github.com/64kramsystem/ray_tracer_challenge-completed
Owner: 64kramsystem
License: cc0-1.0
Created: 2020-10-19T16:48:06.000Z (about 5 years ago)
Default Branch: master
Last Pushed: 2021-02-20T21:55:11.000Z (almost 5 years ago)
Last Synced: 2025-07-04T06:44:53.821Z (6 months ago)
Topics: concurrent-programming, parallel-programming, pragprog, raytracing, rust, rust-lang
Language: Rust
Homepage:
Size: 790 KB
Stars: 1
Watchers: 2
Forks: 0
Open Issues: 0
Metadata Files:
- Readme: README.md
- License: LICENSE

Awesome Lists containing this project

README

# Ray Tracer Challenge Completed project (in Rust)

My completed Ray Tracer Challenge project, written in Rust.

## Overall design

The project has been written with the intention to produce good code, so the design is overall clean and simple.

The APIs (and test suites) are similar, but not equal to the book ones; at the beginning, I thought refactoring made sense, although later I realized that for comparison purposes, matching the book structure would have made comparisons easier.

The most significant difference is that this project's renderer is parallel, therefore, significantly faster than the book reference.

Two functions are unsafe; this has been necessary in order to make the objects tree mutex-free (which allows full parallelism); this unsafe problem has been discussed on the [Rust Programming Language Forum](https://users.rust-lang.org/t/is-it-possible-to-safely-build-a-read-only-thread-safe-bidirectional-tree/52759), and there is no trivial/safe solution.

A change that would simplify the design is to convert the Shape trait into a base class; this is discussed on the trait comment. Also, it would be more readable just to have the owned version of the Matrix/Tuple operations, with a borrowed one for the exceptional cases.

The project is divided in `library`, `macros` and `practice`.

## Demo renderings (from the last chapters)

Chapters 1-13: Shapes and properties