-
Notifications
You must be signed in to change notification settings - Fork 18k
x/sys/windows: add GetFinalPathNameByHandle #41686
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
Comments
|
Hmm, maybe I misunderstood (and if so, great!), but I thought I couldn't import "internal/syscall/windows" (I had gotten a 'can't find import: "internal/syscall/windows"' error message when I tried). If I should be able to import that library, then agreed that it's location in one place or the other is not important to us. |
@iwdgo This issue is about golang.org/x/sys/windows. It is not about internal/sys/windows, which is for internal standard library use and, as @sethkoehler says, can't be imported by third party packages. |
@sethkoehler if you want to add GetFinalPathNameByHandle to golang.org/x/sys/windows package, you have to do it yourself. See https://golang.org/doc/contribute.html for instructions. Alex |
Or Constantin might be able to help, @iwdgo? |
Gobot seems not working syncing CL to this issue |
Thank you for this! Out of curiosity, is there a way to see whether this will make it into Go 1.16 (my understanding is it will have just barely made it in, but I may be not properly understanding the Go release cycle). |
This is a change to the golang.org/x/sys repository, so it's not part of a Go release. Anybody can import it today. |
Also, this seems to be fixed, so closing the issue. |
Ah, that's great, thank you all! |
Change https://golang.org/cl/270459 mentions this issue: |
The function name should be GetFinalPathNameByHandle, not GetFinalPathNameByHandleW, and it should take types in windows, not in syscall. This was merged so recently that I think we can just fix it up here. Updates golang/go#41686 Fixes CL 264577 Change-Id: Ib84df5b5a9c2df5ad4344884874afa152e9ca554 Reviewed-on: https://go-review.googlesource.com/c/sys/+/270459 Trust: Jason A. Donenfeld <[email protected]> Trust: Alex Brainman <[email protected]> Run-TryBot: Jason A. Donenfeld <[email protected]> TryBot-Result: Go Bot <[email protected]> Reviewed-by: Brad Fitzpatrick <[email protected]> Reviewed-by: Alex Brainman <[email protected]>
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Went looking for GetFinalPathNameByHandle to use this as a replacement for EvalSymlinks not working with long filenames (see #40966).
What did you expect to see?
GetFinalPathNameByHandle to exist.
What did you see instead?
It was not there :)
The text was updated successfully, but these errors were encountered: