cmd/compile: what exactly should -L flag do? #36988
Comments
thanks for looking at this... it's significant because IDEs like VSCode cannot click through to the filename listed in the terminal if it is not rooted in the workspace. |
should be an easy one i would think. |
Thank you for the report @jkassis and welcome to the Go project! |
I tried this back to 1.10 and as far as I can tell, |
@aclements Will investigate. |
Note that CL 77090 explicitly states that package main
var _ = int
//line foo.go:42
var x = y
func /*line bar.go:7:1*/ init(int){} (full path
Thus, It shouldn't be difficult to make |
Since We have a variety of options for reporting error positions: file paths can be relative (to cwd) or absolute. And positions can be relative to the most recent We can abbreviate these 4 possible combinations with 4 letters: Currently, without the
With the
where the There are many possible combinations ( I suspect (from the original comment in this issue) that the expectation for
if there's no
if
if there's no
if Comments? |
This issue is currently labeled as early-in-cycle for Go 1.17. |
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
)?macos 10.15.2
go env
OutputWhat did you do?
What did you expect to see?
full paths in the errors list
What did you see instead?
partial paths
The text was updated successfully, but these errors were encountered: