-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
encoding/binary: missing documentation for BigEndian and LittleEndian functions #68083
Comments
Similar Issues (Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.) |
Given the function names are quite self-explanatory, what other information would the function docs contain? |
For example, |
I checked that adding the documentation would work (the bug referenced by gabyhelp made me wonder) so I think a pull request would be fine. There may be some back-and-forth on the exact wording in review, but if it tripped you up, it is probably a problem for other people, and is worth fixing. There's a process, if this is too much, say so (that's also useful feedback) and maybe someone else will write the docs and you can comment on whether that meets your needs. |
They have documentation. https://pkg.go.dev/encoding/binary#pkg-variables |
@rsc the variables When you hover over |
@dr2chase I will look into it this weekend. |
Change https://go.dev/cl/638936 mentions this issue: |
CC @golang/tools-team for awareness of how gopls comes into play here. |
I think gopls is working as intended. The |
Go version
go version go1.22.3 darwin/arm64
Output of
go env
in your module/workspace:It is not important here and contains information about my employer that I do not want to share.
What did you do?
I wanted to use the functions of the
littleEndian
andbigEndian
types and noticed thatgopls
does not provide a function documentation. I was unsure about the exact behavior and needed to look up the implementation.What did you see happen?
gopls
just provides the function definition with description (see here).What did you expect to see?
I wanted to see a documentation of those functions. Would you accept a PR that adds the documentation?
The text was updated successfully, but these errors were encountered: