Clarify TODOs in is_hidden docstring

[kalel-commits]

This PR clarifies existing TODOs by documenting known limitations in the
is_hidden() docstring. No behavior is changed.

[github-actions]

Thank you for the PR! The changelog has not been updated, so here is a friendly reminder to check if you need to add an entry.

[Copilot]

Pull request overview

This PR enhances the docstring of the is_hidden function by documenting current implementation details that correspond to existing TODOs in the code.

Changes:

• Added a note to the is_hidden function docstring explaining that platform-specific checks are performed on each invocation and that bytes inputs are supported for backward compatibility

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[JOJ0]

I might be slow here but what did you intend to clarify? Lines 25-27 tell exactly the same already. Maybe I'm missing something, please elaborate your idea here.

[kalel-commits]

Thanks for the look happy to elaborate the intention here was not to provide any new information, rather to declare the meaning of TODOs that already exists in the docstring.

currently the docstring is an explanation of what the function does, but the TODOs are clues to a couple details that might not be obvious behind this operation:
that a platform-dependent check is performed on each call, and since bytes inputs still have support largely for backwards compatibility.

This note seemed like an attempt to bring that detail out for readers without having them know to go find or understand the TODO comments.

If this does feel a bit redundant or not useful I will drop the changes.