Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Thanks, I forgot about the warnings. It's been a while since I've used Go.


sort by: page size:

Thank you! I didn't think to check the Go docs.

Thx for the info, I don’t use Go typically.

I constantly see users of Go running into these problems. If you haven't, good for you I suppose.

Can you remember even one? I'm interested. I've used Go at Extremely Large Scale (tm) and never thought it was terribly troublesome.

apologies, I was being snarky. Around when I was told to run this command was when I stopped using go.

Thanks for that. It's been a while since I used Go. That is quite nice.

Thank you, I've just checked go again, that's really cool. I'm going to use it.

Or better solution, don't use Go.

What about using Go?

Sorry, that's goalpost hiking. You said they didn't provide an automated transition tool, not that it wasn't perfect. Go's tools will only issue warnings in some cases too, so I'm really lost as to what you think you're saying here.

It seems to follow that you shouldn't use Go in HPC. Which is also fine.

I thought this was already deprecated? I remember updating my docs a couple of months ago when Go 1.16 came out.

Oooooh, good point. I had forgotten you used Go, actually.

I've been working with Go for 4 years and I've not encountered it. Perhaps there was an edge case where it was allowed, but I don't recall it.

Oh, thanks for the info, didn't know that. Still I don't think that Go should have that feature.

i actually don't think the Go version is bad. I can very clearly see what is happening and I can also do something with the error

Cool service. Heads up, your Go version is really out of date with some potentially serious security holes. You should probably upgrade to 1.10

With the obvious downside that you are now writing your application in Go.

Can you elaborate, RE: the Go code review?
next

Legal | privacy