On 2/25/21 8:31 AM, Brian Candler wrote:
> I suggest that newcomers are told to create an empty directory, create main.go
> in that directory, and then use "go run ." (a literal dot), "go build .", "go
> fmt ." etc. Of course, this means that if you have several programs you need
> to
> create se
Hi Volker,
> On 25. Feb, 2021, at 09:34, Volker Dobler wrote:
>
> Well, there is already subcommand "test": go test runs the (unit) tests
> defined in the *_test.go files using package testing, so this won't work.
>
> Well there is nothing wrong with a plain "go run" (nor arguments at all)
> or
On Thu, 25 Feb 2021 at 09:08, Paul Förster wrote:
> Hi Volker,
>
> > On 25. Feb, 2021, at 08:46, Volker Dobler
> wrote:
> >
> > I think there is a major problem with "go run main.go": It creates
> > a _false mental model_ of how Go code is built and executed in the
> > minds of _beginners_.
>
>
For me, it took a while to twig that the normal unit of compilation is the
package, *and* that a package is normally a *directory* of files. "go run
main.go" breaks this by having a special case where the package is a single
file (or worse, a collection of listed files).
I suggest that newcome
Hi Volker,
> On 25. Feb, 2021, at 08:46, Volker Dobler wrote:
>
> I think there is a major problem with "go run main.go": It creates
> a _false mental model_ of how Go code is built and executed in the
> minds of _beginners_.
I am a Go newbie and I agree, though I immediately understood that "g
Hello everyone,
I'm Lorenzo and I'm not a computer scientist, I have used some "Matlab" and
I am new with Go (surprisingly fast, simple and elegant).
I'm trying to do some basic operation on matrix with the "Gonum" package
using vectorization. I was curious about the speed of development and the
