Skip to content

Initialize the FOV buffer for out-of-bounds points of view - #199

Open
mmporong wants to merge 1 commit into
libtcod:mainfrom
mmporong:fix/initialize-fov-buffer
Open

mmporong wants to merge 1 commit into
libtcod:mainfrom
mmporong:fix/initialize-fov-buffer

Conversation

@mmporong

Copy link
Copy Markdown

Initialize the temporary FOV map buffer to zero so an out-of-bounds point of view cannot return uninitialized visibility flags.

compute_fov() currently warns about an out-of-bounds point of view and continues. libtcod then returns an error without filling the FOV cells. Since the wrapper allocates those cells with np.empty, the result can contain stale visibility data. Zero-initialization preserves the existing warning behavior and returns an all-false mask in this case.

The regression tests cover all four map boundaries with a poisoned allocation so the failure is deterministic. All four fail before the fix. After the fix, these tests and the existing map tests pass (9 passed). Ruff reports no issues on the changed source and test files.

Validation used the tcod 21.2.2 wheel with only tcod/map.py replaced by the updated file. Before the change, that file was byte-for-byte identical to the current source. A full source build and rendering tests were not run.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant