I also forgot to mention one thing. I was able to build the program using go build. Even the executable was there. It just didn't run until I connected to internet.
On Wednesday, April 8, 2020 at 10:17:36 PM UTC+6, Tanmay Das wrote: > > Hey Gophers, > My very first post here. > > Today I faced an unexpected power outage and I wanted to tinker with Go a > little bit. I wrote a simple hello world program and ran > go run helloworld.go > > Strangely the code didn't run. In fact, the terminal prompt never exited. > I kept running the same command over and over again but no luck. I checked > all my configurations, my env vars, etc. and everything was ok. After > ruling out all the possibilities it suddenly hit me: what if Go actually > requires an internet connection to run a program for no apparent reason? I > waited for the electricity to come back and as soon as I was connected to > the internet I ran `go run` command again and voilà! > > Is this behavior expected? If it is, why did the go authors make such a > decision? I mean making the internet connectivity a dependency for the > execution of a program sounds counter-productive to me, honestly. :( > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/e8bfd7c9-206c-4b7e-b420-96753a3da726%40googlegroups.com.
