Skip to content

minors typos in the repo #60

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Nitish-bot wants to merge 2 commits into
base: main
Choose a base branch
from
+2 −2
Open

minors typos in the repo #60

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ea9fe8a
typo in docs
Nitish-bot Jan 12, 2026
31e384d
also typo i think
Nitish-bot Jan 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion crates/processing_pyo3/examples/animated_mesh.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
geometry = None
grid_size = 20
spacing = 10.0
offset = (grid_size * spacing) / 2.0;
offset = (grid_size * spacing) / 2.0
time = 0.0

def setup():
Expand Down
2 changes: 1 addition & 1 deletion docs/principles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ user-facing API via an overload.
We never return pointers to data that lives in libprocessing. Because we use the ECS to manage Rust data, where longer
lifetimes are necessary we return an `Entity` id, which can be returned to the user as a `u64` containing both the index
and generation of the ECS entity. Any data not representing an API-level object should be returned on the stack and
where an allocation is necessary (e.g. buffers for pixel data), it's the responsibility of the consumer to allocate a
where an allocation is necessary (e.g. buffers for pixel data), it's the responsibility of the consumer to allocate and
provide the pointer to the requisite allocation.

API-level objects should wrap ids and they should never be exposed to the user as a first-class concept. All data which
Expand Down