On Thu, Feb 3, 2022 at 7:07 PM Paulo Júnior wrote:
>
> Hi all.
>
> I hope you are well.
>
> Is there a big difference, in terms of performance or functionality, between
> declaring []*Person or []Person as a return type of a function?
If you find yourself iterating over a group of structs like t
I'm trying to wrap my head around modules.
When importing other packages into my project, there is a module prefix.
For example,
import (
"example.com/potato/tomato"
)
will import the "tomato" package from the "example.com/potato" module.
But this whole time as I've been learni
Oops, I see another reply to this thread linked to a document that has a better
description of what I stumbled through. :-)
Connor
--
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,
> On Aug 26, 2021, at 5:21 PM, Paul S. R. Chisholm
> wrote:
>
> Hypothetical example: Say I'm writing an application that uses "rsc.io/quote"
> and I discover a bug in that package that breaks my software. I would of
> course clone the quote repository, add a test that demonstrates the bug,
> On Aug 22, 2021, at 10:11 PM, jlfo...@berkeley.edu
> wrote:
>
>
> I've noticed that few, if any, Go programs use Makefiles. Is that because the
> overhead of using make is greater than the overhead of just always compiling
> and linking everything?
> One piece of evidence for this is tha
> On Aug 14, 2021, at 11:37 AM, Денис Мухортов
> wrote:
>
> I started studying interfaces, tried to write them in different ways, but I
> don't understand what I'm doing wrong. In the first case, everything works,
> but I don't understand why it doesn't work in the second
> SECOND
> packag
