w2 | wc -l
> 257
>
> Don't know that this is very telling.
>
> Is there another important metric as far as go compilation? Or another
> compiler option to see numbers branches or the like which could point up
> something?
>
>
> On Monday, August 15, 2016 at 1:40:
Listen and serve is just a wrapper around serve with a provided listener.
Create the listener then pass it to serve, at that point you know the socket is
open and will accept connections into its backlog.
--
You received this message because you are subscribed to the Google Groups
Alternatively, make a connection to your server locally to check it is
listening, the fire off the browser.
--
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
I haven't run the code under the race detector (hint, do this and you'll have
the official answer) but I don't believe wg.Wait creates a happens before event
that ensures the assignment to result will be visible to other goroutine.
--
You received this message because you are subscribed to
Additionally in unix, where the name comes from, a file may have many names
(many hard links to a directory entry) so remove in this case is removing a
directory entry. Separately, when the link count of a file drops to zero, the
file is now inaccessible as you cannot link to something that
On Sunday, 26 February 2017 16:54:25 UTC+11, Oleg Puchinin wrote:
>
> Hello !
> What is wrong and how to do it ?
>
What did you expect to happen? What happened instead?
>
> func handleconnection(tcp net.Conn) {
> cmd := exec.Command("/bin/bash")
> cmd.Stdin = tcp
> cmd.Stdout =
Yup. A syscall causes the scheduler to create a new thread that replaces the
one blocking on the syscall.
--
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
Your spinning goroutine is block the garbage collector which needs to stop,
temporarily, all the running goroutines to make love objects.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails
The oscar for worst autocorrect in a technical debate goes too ...
On Thursday, 2 March 2017 21:04:16 UTC+11, Michael Jones wrote:
>
> Go deserves a keyword to "make love objects."
>
> On Thu, Mar 2, 2017 at 9:47 AM Dave Cheney <da...@cheney.net >
> wrote:
>
&
No, that's is not thread safe. The race detector will spot that.
--
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.
For
Not really. Runtime.KeepAlive is special, it'll continue to be special in the
future.
--
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
It looks like they've exported GOARCH=x86_64 which is the linux preferred
word for amd64. They should either remove the GOARCH setting or set it to
GOARCH=amd64
On Thursday, 1 September 2016 10:19:35 UTC+10, kortschak wrote:
>
> One of my users has struck a problem with an install of go1.7 from
Please redirect this question to golang-nuts.
On Sun, Sep 4, 2016 at 7:22 AM, Ринат Галиев wrote:
> Hi, i need to solve the task:
> Change the program so that the numbers 1 through 6 were printed to the
> console in order. Allowed to amend the sections of code that are
Are you sure that goroutines are exiting? You can check this in the
/debug/pprof handler. It will tell you how many goroutines are currently
running.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop
t;
>
> 在 2016年9月6日星期二 UTC+8下午4:25:40,Dave Cheney写道:
>>
>> This error handling looks wrong,
>>
>>
>> https://gist.github.com/aiden0z/b8cf00953e81f778bd584fa2ff7eaae7#file-server-go-L268
>>
>> Any error from socketio is ignored, and the method alwa
me.goexit took so many memory.
>
>
> 在 2016年9月6日星期二 UTC+8上午11:07:42,Dave Cheney写道:
>>
>> It looks like your application is using 4.5gb of ram. Check the number of
>> sockets and goroutines you have running. If there are no timeouts then the
>> goroutines
Here's the same program rewritten.
https://play.golang.org/p/ANHNUcPjR2
If ch is writable, then select pseudo randomly chooses the first or second
case. The default case is never taken unless ch is blocked, in which case the
goroutine will block sending to ch indefinitely.
--
You received
Also, heap released will not grow until you stop the memory leak and enough of
the heap remains idle for more than 10 minutes.
--
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,
The log package has some benchmarks, maybe make the change and see if it
makes a difference.
On Wednesday, 7 September 2016 02:46:09 UTC+10, mwor...@gmail.com wrote:
>
> Hey, It's commented "release lock while getting caller info - it's
> expensive" in source code of /src/log/log.go line:150.
>
function godoc {
${GOBIN:-${GOROOT}/bin}/godoc $@ | ${PAGER:-less}
}
On Friday, 2 September 2016 10:40:42 UTC+10, anatoly techtonik wrote:
>
> And why is that? Is it because it is impossible to reliably detect
> interactive user session?
>
> On Thursday, February 16, 2012 at 1:25:28 AM
Inlining is conservative. As well as the size of the code being inlined,
current 40 units (unit has not scale), some operations are not inlined, as
they are considered hairy. switch used to be considered hairy, 1.7 fixed
that, for is still hairy.
On Tuesday, 30 August 2016 15:58:30 UTC+10,
Unfortunately POSIX does not guarantee that close from one thread will unblock
another.
--
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
Sep 2016, at 19:41, Russel Winder <rus...@winder.org.uk> wrote:
>
>> On Mon, 2016-09-12 at 17:21 +1000, Dave Cheney wrote:
>> Distros are always out of date, sometimes hilariously. Official in my
>> parlance means "from the go team"
>
> If the o
I'm sorry to hear that you're having issues. The Go tool should detect that
a cached package in $GOPATH/pkg is out of date and overwrite it. If this is
not happening reliably this may be a bug.
Can you give some details about what you tried, what you expected to happen
and what happened
A mips32 port is in the
works, https://groups.google.com/forum/#!topic/golang-dev/GDtW0vCretE
On Saturday, 10 September 2016 18:33:11 UTC+10, ff...@gmx.us wrote:
>
>
>
> Le lundi 21 décembre 2015 19:01:25 UTC+1, Manlio Perillo a écrit :
>>
>> ...
>> Only arm and mingw toolchains are available,
https://play.golang.org/p/RthMnILvkP
func main() {
inf := float32(math.Inf(+1))
fmt.Println(inf)
}
On Sunday, 11 September 2016 15:58:04 UTC+10, bradfitz wrote:
>
> Not beautiful, but...
>
> https://play.golang.org/p/WWEEJN8LcF
>
> func main() {
> i32 := math.Float32frombits(0x7F80)
>
I'm glad you found the cause of the leak.
--
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.
For more options, visit
You're ignoring the error from time.Parse, that will tell you what went wrong.
--
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
I'm sorry you've not enjoyed Go. How to uninstall Go will depend on how you
installed it. I'll give tree options, if they do not apply, please reply
with more detail about how you installed Go.
1. If you installed Go via homebrew, which is quite common, use the brew
command to uninstall Go
2.
I don't think it's about the installation of the tools. The problem you've
described sounds like you have tools that use the compiled form of the package,
but your development process has not embraced go install so what you go build
the later test is not the same thing.
--
You received this
It depends who can see that variable, if this is a global variable, or its
address has been taken it is not safe. If the variable is private the goroutine
then it is safe becase there is no race on private variables. Remember a
variable of type chan is just a pointer.
--
You received this
> Since Go is battery included and http is part of its core library,
We said batteries, not the kitchen sink.
But seriously, the standard library gives you the components to build these
tools yourself. If the Go distro included a http server that just served
static files, while this would be
Stick an @ at the start of the file name, or the socket will remain on disk
after the process has exited.
--
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
It's a Linux thing, Google abstract domain socket.
--
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.
For more options,
wide. One of values that it returns identifies
> that if the mutex is already created by other instance, or it's the first
> time it's being created on this system.
>
> Is there something similar on Linux?
>
> On Tuesday, July 19, 2011 at 3:55:45 PM UTC+4:30, Dave Cheney wrote:
>
bt, to serialise a structure with encoding/json or encoding/xml (and
anything else which uses reflect) the fields have to be public (start with
a capital letter) anyway, so that breaks the deadlock with keywords of the
same name.
On Wednesday, 5 October 2016 02:54:32 UTC+11, David Luu
Centos 5 is not supported, the kernel is too old. Sorry.
--
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.
For more
Yes. The bottom.
--
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.
For more options, visit
ok, that sounds like a different problem. Some tools use the cached (.a
file in the pkg/ directory) version others use the src directly. If you
don't install, the tools that use the .a version will be out of date (at
best) or fail (at worse).
Really, you want to use go install, just trust me
Move http.ListenAndServe to the top of the main() function, outside the
http.HandleFunc call and it will work.
On Sunday, 18 September 2016 05:50:03 UTC+10, loc...@gmail.com wrote:
>
> Hello everyone,
>
> I am using Go version 1.7.1 on a 32-bit version of Windows 10 and cannot
> view the
Break breaks out of the select, not the for. Return would work here, or you
could use a labled break.
--
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
What did you expect to happen when you ran this program?
What happened instead?
--
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
What did you expect to see when you ran that code?
What did you see instead?
--
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
int
> where I'm not expecting it, which is preventing capture of a good profile.
>
> On Monday, September 19, 2016 at 5:18:56 PM UTC-5, Dave Cheney wrote:
>>
>> Try b.ReportAllocs() before your benchmark loop. That's the easiest way
>> to benchmark the allocations per
I'm sorry this did not fix your problem. Can you please try to explain your
problem, I don't think I understand what the issue you are having is.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving
Try b.ReportAllocs() before your benchmark loop. That's the easiest way to
benchmark the allocations per operation.
--
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
Whenever you suspect memory corruption, try the race detector.
Can you also please post the full panic message, you cut off the important
part
On Friday, 26 August 2016 01:11:49 UTC+10, arb...@gmail.com wrote:
>
> Hello everyone,
>
> My application occasionally crash when processing string
runtime/mfinal.go:464
On Friday, 26 August 2016 19:56:49 UTC+10, Cholerae Hu wrote:
>
> I'm curious that how does compiler recognize runtime.KeepAlive specially?
>
> 在 2016年8月26日星期五 UTC+8上午12:04:57,Ian Lance Taylor写道:
>>
>> On Thu, Aug 25, 2016 at 12:15 AM, Cholerae Hu
>>
Try listening on 127.0.0.1 not localhost, on osx at least this avoids the alert
because it avoids the DNS lookup.
--
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
Be careful that the compiler isnt removing some or all of your program. Check
the asm to assert that your program is not being optimised away.
Then check -gcflags=-m to see if the compiler is choosing a different escape
analysis depending on the size of your allocation.
--
You received this
Don't forget to log that issue.
--
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.
For more options, visit
s/go build/go install/g
On Thursday, 29 September 2016 01:41:31 UTC+10, Micky wrote:
>
> go list ...
> go build ...
>
> It will build only if it it needs to! Otherwise add -a to force.
>
> On Wed, Sep 28, 2016 at 8:30 PM, Tim K
> wrote:
>
>> OK, so all that should happen is
Sorry, I misspoke, this logic does not apply to map lookup, they are unrelated
other than having a one arg and two arg form.
--
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
Which of these would you prefer happened instead?
* A failed type assertion always panic'd
* A failed type assertion never panic'd and instead returned the zero value, as
the map lookup does
* Something else
Dave
--
You received this message because you are subscribed to the Google Groups
If you think that's inconsistent, you should see how we used to delete things
from maps ;)
--
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
It's all in the release history, this change occured before Go 1.0.
--
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.
For
That sounds like a very bad idea. You type assert to the wrong type and receive
a valid blank value for that type. If you're lucky the program crahesh
immedialy because the type's zero value is nil, if you're not the person
program continues to execute using this types zero value for an unknown
This is usually caused by the process writing to a log file that has been
deleted. This is a very common bug with programs that rotate their own logs and
a major reason why 12 factor apps recommend that log rotation be down by an
external program.
Have a look in /proc/yourprocess/fd with ls
One way to do this might be to enable memory profiling in your program with the
rate set to 1. Hopefully this will record the stack trace of every allocation.
The data may need some interpretation
--
You received this message because you are subscribed to the Google Groups
"golang-nuts"
king
> v := iface.(someType)
> semantically equivalent to
> v, _ := iface.(someType)
> 'cause I don't see any.
>
> On Thu, Sep 29, 2016 at 11:40 AM, Dave Cheney <d...@cheney.net> wrote:
>
>> A type assertion is dangerous because if the thing you are asserting to
>> doesn't
Sorry, you'll have to work harder to generate a memory profile. My
github.com/pkg/profile package may help automate some of the work, but may
introduce a few allocations of its own which you will have to filter out.
--
You received this message because you are subscribed to the Google Groups
-gcflags=-m is your guide. There are no documents of the escape analysis done
by the gc compiler, but you could read the source of
cmd/compile/internal/gc/esc.go
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group
wrote:
> On Thu, Sep 29, 2016 at 9:31 AM, Dave Cheney <d...@cheney.net> wrote:
>
>> Sorry, I misspoke, this logic does not apply to map lookup
>
>
> But why? It seems to me, everything you said can just as easily be applied
> to map lookups. Why is a zero-value on a ty
Which version of Go?
On Thursday, 29 September 2016 00:18:29 UTC+10, 刘桂祥 wrote:
>
> // example1.go
> package main
>
>
> func main() {
>
> for i := 0; i < 2; i++ {
> m := make(map[int]int)
>
r(uintptr(Pointer()) + 8
> }
>
> and add debug info to runtime/mallocgc.go file
> here is the output:
>
> debug
> mallocgc: 8
> mallocgc return2: 0xc20800a220
> 0xc208039f68 (0xa00a0,0xc20800a220)
> mallocgc: 3
> mallocgc return2: 0xc20800a230
> debug1 100 0xc208039f
Did you find the open deleted file in /proc/.../fds ?
On Thursday, 29 September 2016 22:37:47 UTC+10, ramkumar.g...@gmail.com
wrote:
>
> So it looks like a bug in the glog library. Anyway to file a bug against
> it?
--
You received this message because you are subscribed to the Google Groups
http://talks.godoc.org/github.com/davecheney/high-performance-go-workshop/high-performance-go-workshop.slide#36
See also think linked issue at the bottom of the slide.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this
There are already too many ways to declare and or assign a variable in Go.
Adding more is not a solution.
--
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
What is the exact command you and your friend are using to build your project?
--
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
-build
On Monday, 7 November 2016 05:12:55 UTC+11, gkol...@gmail.com wrote:
>
> go build main.go
>
> On Sunday, November 6, 2016 at 1:21:24 AM UTC-5, Dave Cheney wrote:
>>
>> What is the exact command you and your friend are using to build your
>> project?
>
>
-
and function/method parameters, and named return arguments.
On Wednesday, 9 November 2016 23:13:36 UTC+11, Jan Mercl wrote:
>
> On Wed, Nov 9, 2016 at 1:00 PM T L
> wrote:
>
> > many? I see only two ones.
>
> v := expr
> var v = expr
> var v T
> var v T = expr
>
> --
>
> -j
Can you please post the full stack trace of the crash and a piece of code
to reproduce the issue.
Thanks.
On Thursday, 10 November 2016 00:26:03 UTC+11, nova...@gmail.com wrote:
>
> Hi i am using Google Cloud vision API in my server side (JAVA) but when no
> results found my server got crashed
The garbage collector only runs when your program creates garbage -- the
more your program allocates, the harder the garbage collector will work.
On Thursday, 10 November 2016 15:31:24 UTC+11, vyasgir...@gmail.com wrote:
>
> Is there a way to overwork the garbage collector in go lang?
>
--
I'm afraid not, pprof does not record that information.
--
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.
For more
The runtime does not give any guarentee when you use a go statement if the
goroutine being spawned will run immediately, or if control will remain
with the original goroutine.
This program, https://play.golang.org/p/-OcCzgt4Jy, which pauses all
goroutines while they are being created exhibits
Can you post a runable sample so that other can try to reproduce your issue?
On Friday, 11 November 2016 12:06:21 UTC+11, Evan Digby wrote:
>
> Is it expected that if multiple sub-benchmarks are run in the same
> benchmark, the cost of the setup will impact the results from the first
>
Are you able to post a piece of sampl code which reproduces the problem?
--
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
Yup, totally av.
To demonstrate this, use the -x flag, that will show you, just by the named
eye, which commands are being delayed by your av software.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop
For some background, I'm trying to flesh out the concerns of the various
personas who would interact with a central repository.
https://docs.google.com/document/d/10jbJLkmQgpi1CxHKuO75Av1tKYgtOBSjzX5Z9hnG0vI/edit?usp=sharing
On Thursday, 20 October 2016 17:43:08 UTC+9, Dave Cheney wrote:
>
T L, I often hear this comment when a central repo for Go is
proposed/suggested/requested. Are you able to give details of the things
you do not like about Maven/npm/rubygems central repos. The most specific
the better please.
On Thursday, 20 October 2016 16:23:09 UTC+9, T L wrote:
>
>
>
> On
What is a pointer wrapper value?
in all seriousness, if you review the git history of the Go spec you'll
find the word "reference" was purged about two years ago, in effect, to try
to stem these discussions.
On Thursday, 20 October 2016 16:07:07 UTC+9, T L wrote:
>
>
>
> On Thursday, October
There are no server class arm64 boards in your price range, sorry.
If you want server class hardware you should look to Cavium or ARM
themselves, these development systems start at the several thousand US
dollar price range.
If you want something in the $400 mark, http://www.96boards.org/
If you want to do power comparisons you should probably do an apples to apples
comparison. Just like you wouldn't deploy your app on an Intel netbook powered
by an ancient celeron, you wouldn't deploy your app on a consumer level odroid
development board.
It's also important to remember that
Yes, http://dave.cheney.net/2015/08/22/cross-compilation-with-go-1-5
On Monday, 24 October 2016 02:08:07 UTC+11, Carlos Ferreira wrote:
>
> Is there a way to cross-compile Go Code to an arm platform, for example, a
> Raspberry Pi 3?
>
>
--
You received this message because you are subscribed
running arm64 mode at the moment. This is a
limitation of the kernel as shipped by the Raspberry Pi foundation.
>
> Ibrahim, no, I want to play with ARM. I have many intel boards.
>
> Thanks
> dharani
>
> On Sat, Oct 22, 2016 at 11:46 PM, Dave Cheney <da...@cheney.ne
re 32 bit systems with a 2G/2G user/kernel address space
split.
>
> Thanks
> dharani
>
> On Sat, Oct 22, 2016 at 11:46 PM, Dave Cheney <da...@cheney.net
> > wrote:
>
>> There are no server class arm64 boards in your price range, sorry.
>>
>
os.Exec is thread safe.
--
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.
For more options, visit
You have to depend on golang.org/x/net/http2 to opt in
https://github.com/davecheney/httpstat/blob/master/main.go#L252
On Wednesday, 26 October 2016 03:46:31 UTC+11, Moshe Litvin wrote:
>
> The code in net/http/transport.go (onceSetNextProtoDefaults) contain:
>
> if t.TLSClientConfig != nil ||
Unless you have built Go from source and/or your user owns the path Go is
installed in, this is one of the few cases where go build is recommended
over go install.
http://dave.cheney.net/2015/08/22/cross-compilation-with-go-1-5
On Wednesday, 26 October 2016 05:09:18 UTC+11, Liam wrote:
>
> I
Cool. Thanks for figuring it out and posting your answer.
On Tuesday, 15 November 2016 07:28:16 UTC+11, Evan Digby wrote:
>
> Confirmed bug on my part.
>
> When using the "..." suffix to pass a slice into a func with variadic args
> it passes through the the original slice, rather than
I think you problem is here
jsonReservations, err :=
jsonConvert.ReservationsJson(otherReservations)
if err != nil {
rw.WriteHeader(http.StatusExpectationFailed)
fmt.Println(err)
}
Instead try this
if err != nil {
On Saturday, 26 November 2016 08:00:24 UTC+11, Roger Alsing wrote:
>
> So it works very similar to normal OS thread context switching, but more
> explicit?
>
Yes, goroutine switching occurs a known points; effectively where the
goroutine is blocked from proceeding; sending and receiving on
Would a type switch do what you want ?
err := fn()
switch err := err.(type) {
case nil:
// all good
case *MyCustomError:
// do something custom
default:
// unexpected error
}
On Saturday, 26 November 2016 05:07:55 UTC+11, Parveen Kumar wrote:
>
> Hi Team,
>
> I want to catch my custom
This is extremely common in go code, vet is being pedantic,
--
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.
For more
With a nod to Chris's excellent presentation, this may be an example of Go
breaking its own orthogonality rules for the sake of being more consistent (the
rule of least surprise)
There is a strong overlap between an interface with a single method and a
function value, Tomás Senart spoke about
My vote is for "in the package that needs them"
On Tuesday, 22 November 2016 02:30:21 UTC+11, Vorn Mom wrote:
>
> Sorry if it was asked before, but where should interfaces live?
>
>- In the package that contains an implementation of it.
>- In its own package.
>- or in the package that
Why do you want to use LockOSthread, you've proved it has a significant
performance cost for your application.
--
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
Please try profiling your application, if you are on Linux perf(1) works very
well for tracing user and system time.
--
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
Related, you don't need a pointer to a chan, channels are already pointers to
the private runtime channel type.
--
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
Please do not reopen to a four year old thread. Instead please start a new
thread describing the problem you have, what you tried, and what happened when
you tried.
Thanks
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from
101 - 200 of 647 matches
Mail list logo