As much as it hurts the C hacker inside me we have settled on using `_internal` to mark private function names that clash with a public function of the same name. Introduce a policy section and rename one instance, I did not grep the codebase looking for other violations. This came up because I had to look at what `_inner` implied when reading the function name somewhere else. |
||
---|---|---|
.. | ||
contrib | ||
embedded | ||
examples | ||
src | ||
tests | ||
CHANGELOG.md | ||
Cargo.toml | ||
build.rs |