Hi Kazuya,
I'm not sure what you mean by "learn how to write go documentation".
* Do you want guidelines for contributing to the official documentation?
* Do want a guide for how to write documentation for your own packages?
I guess a lot of the experienced people here can give you tips, but
I'd
First of all let's not confuse Go's Interfaces with Java's class
inheritance.
Read again the definition from the link you sent:
"An interface type specifies a method set called its interface. A variable
of interface type can store a value of any type with a method set that is
any superset of the
Are you compiling both files together?
a.go
package main
var Number int
-
---b.go
package main
import "fmt"
func main() {
Number = 1
fmt.Println(Number)
}
-
go build a.go b.go
On Thu, Jan 24, 2019 at 3:16 PM Michael Banzon wrote:
> Can you provide the out
Kazuya,
That makes no sense.
The main package is the point of entry to an executable. This is where
things happen.
You create packages that are able to do things and you use them in the main
package to some purpose.
It's going against to the reason why packages are there.
What you're asking is
Kazuya,
I've been following or questions for a while and the common pattern I see
is: You make it feel like we're doing homework for you.
Right now you're just throwing a bunch of questions at the group and
waiting for an answer.
For example, this question could have been something like:
"I was
Actually I have the email here from three days ago, so it might have been
marked as spam at some inboxes
2017/10/10 2:02 "Ian Lance Taylor" :
> On Mon, Oct 9, 2017 at 9:54 AM, jimmy frasche
> wrote:
> >
> > I didn't get that email either.
> >
> > On Mon, Oct 9, 2017 at 9:51 AM, Jan Mercl <0xj...
Hi there
If I got it right, all you wanna do is calculate the decibels of an audio
file and trigger an an alert in case it goes over a certain threshold.
I found this great answer on Stack overflow, really recommend the whole
read but I'll add here the TL;DR, however I do recommend the full read
