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
cmd/compile: constant inlining happens even when disabling inlining and optimizations #35527
Comments
Non-integer constants are never exported to debug_info, it doesn't have anything to do with whether they are inlined or not. Also, I'm not sure it's worth the executable bloat costs, since IIRC there was no way to reuse the strings stored in rodata from the debug_info constant entries. @gopherbot please add label Debugging |
Thanks for the explanation. The problem was reported to GoLand by a user that had a similar code like the one above. I'm not sure if go-delve/delve#1753 is related or not. |
When I debug this code: and hover at the constant variables, the value doesn't appear. I have to find the definitions what exactly the value is. |
@kzhui125 that doesn't have anything to do with this issue and should be reported to GoLand. |
I am using VSCode, I have reported this issue in vscode-go extension. I was told this is upstream issue. @aarzilli |
You're right, I was confusing this with a different issue. |
What version of Go are you using (
go version
)?go1.13.4
Does this issue reproduce with the latest release?
I haven't tried with Go 1.14 yet
What operating system and processor architecture are you using (
go env
)?windows/amd64
What did you do?
What did you expect to see?
A boolean result
What did you see instead?
The text was updated successfully, but these errors were encountered: