Did you type exactly go build main.go? It looks like you typed go build main.

I'm having a similar problem. I keep getting can't load package: package .: no Go files in C:\Users\***** every time I try to use the go build command

@dylan844r What precisely do you do?

@ianlancetaylor C:\Users\shumb>go build C:\Users\shumb>go build can't load package: package .: no Go files in C:\Users\shumb I was trying to use this after successfully using the go get tool. I've been stuck here for a while and haven't found any answers on google

@dylan844r The formatting is a bit wonky but it looks like you ran a simple go build. When you run go build with no arguments, it will build the package in your current directory. In you case it is telling you that there is no package in your current directory.

If you ran go get github.com/x/y, then you can build that by running go build github.com/x/y.

This is not the same problem as the original issue here, which does not say no Go files but instead says cannot find package main. Let's take discussion of this side issue elsewhere, preferably a forum; see https://golang.org/wiki/Questions. Thanks.

@ianlancetaylor Yes I did type it correctly. Sorry for not answering earlier, I was very busy with oher things

I actually did type go build main.go, I just don't know why that happens.

I can recreate the problem exactly if I type

go build main

I cannot recreate it if I type

go build main.go

I don't know why you are seeing what you are seeing.

@JZafrag, please fill out the complete issue template. (You can get a fresh copy from https://golang.org/issue/new.)

In order to diagnose the problem, we need to know the Go version in use, the output of go env, and the directory layout of your source code (especially in relation to GOPATH, GOROOT, and any go.mod file that may be present).

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)