Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
I see what you mean and it seems like a simple enough request, but given that it's more of a common function that is used internally for the samples rather than the public-facing API, I'm not sure it's worth changing in all of the locations that the function gets called.
Because then you'll have to go test all of the samples again just to make sure the find+replace didn't accidentally break anything just for a name change instead of a functionality change
Since this likely won't be fixed, I'd rather not keep it open at the moment. Perhaps it can be re-opened down the line or a new issue can be opened if it comes up again.
It's just easier to maintain the issues this way, keeping issues that will be fixed but aren't yet solved open as a pseudo TO-DO list