# Remove non-null assertion in \`CacheHash.release\(\)\` · gitcafe/zig

[View on GitCafe](https://git.cafe/gitcafe/zig/commit/be69e8e871d26973c644cfad5225ae9e337179c9)

Repository: [gitcafe/zig](https://git.cafe/gitcafe/zig)

Visibility: public

Requested revision: be69e8e871d26973c644cfad5225ae9e337179c9

Requested commit: be69e8e871d26973c644cfad5225ae9e337179c9

Commit: be69e8e871d26973c644cfad5225ae9e337179c9

Tree: d5ebab60fa48be4ff42705731de16d561e80c16d

Author: LeRoyce Pearson

Committer: Andrew Kelley

## Message

```
Remove non-null assertion in `CacheHash.release()`

People using the API as intended would never trigger this assertion
anyway, but if someone has a non standard use case, I see no reason
to make the program panic.

```

## Parents

- [e6a37ed94193faf6450a0888c23168a83e914955](https://git.cafe/gitcafe/zig/commit/e6a37ed94193faf6450a0888c23168a83e914955?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zig/tree/be69e8e871d26973c644cfad5225ae9e337179c9?format=markdown)
