Re: [go-nuts] using or extending or forking+renaming github.com/google/licensecheck to provide similar functionality

2019-11-13 Thread fgergo
func Cover(input []byte, opts Options) (Coverage, bool) in licensecheck currently reports len(input)/len(one of the licenses) for each known license. I'd need for all known licenses len(known license)/len(license reference in input). I'd like to scan >10 files (possibly a lot more), where some

Re: [go-nuts] go.dev is live!

2019-11-13 Thread Dan Kortschak
Also, the license feedback link at https://pkg.go.dev/license-policy fails to work on Firefox. On Thu, 2019-11-14 at 15:24 +1030, Dan Kortschak wrote: > Hi, > > It looks like license detection needs work. > > See https://pkg.go.dev/gonum.org/v1/gonum?tab=overview and note it > has > a BSD 3 clau

[go-nuts] Re: [golang-dev] go.dev is live!

2019-11-13 Thread Dan Kortschak
Hi, It looks like license detection needs work. See https://pkg.go.dev/gonum.org/v1/gonum?tab=overview and note it has a BSD 3 clause, as shown by GitHub's assessment (just above the "Clone or download" button) at https://github.com/gonum/gonum and the LICENSE file that it links to. Dan On Wed,

[go-nuts] Re: [golang-dev] go.dev is live!

2019-11-13 Thread Tyler Compton
Thanks for posting! I'm really impressed the website, and with the package view especially. I foresee myself using this instead of godoc.org from now on. I'm curious to hear more about the team's future plans for golang.org. Do you have any plans to migrate or mirror content like the blog or the d

[go-nuts] Question: package rename

2019-11-13 Thread awh6al
Hi gophers, i have a question about renaming a package like `debug/plan9obj` to `p9` with a required changes in the package files. I got a `can't load package` message from `go test -v debug/p9` command, any ideas? -- You received this message because you are subscribed to the Google Groups "

Re: [go-nuts] Go gouroutines vs Rust threads

2019-11-13 Thread Serge Hulne
Thank you! On Wed 13 Nov 2019 at 21:08, Russel Winder wrote: > On Wed, 2019-11-13 at 06:02 -0800, Serge Hulne wrote: > > Am I therefore correct in assuming that, if the problem I am trying to > model > > is not IO bound or CPU bound, but deals essentially with modeling a large > > number of ind

Re: [go-nuts] Should I return an error object, or a pointer to an error object?

2019-11-13 Thread Brian Candler
Thanks. It's much clearer now. Cheers, Brian. -- 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. To view this discussion

Re: [go-nuts] Should I return an error object, or a pointer to an error object?

2019-11-13 Thread Ian Lance Taylor
On Wed, Nov 13, 2019 at 12:23 PM Brian Candler wrote: > > > the current implementation of interfaces is that they always store pointer > > values. If you store a non-pointer value in an interface, that value > > is copied into memory, and a pointer to that memory is stored in the > > interface. >

Re: [go-nuts] using or extending or forking+renaming github.com/google/licensecheck to provide similar functionality

2019-11-13 Thread Rob Pike
Can you please explain in more detail what you're asking for? I don't understand the problem you have or why the current package cannot handle it. -rob On Wed, Nov 13, 2019 at 7:05 PM wrote: > Hi, > > "licensecheck classifies license files and heuristically determines > how well they correspo

Re: [go-nuts] Should I return an error object, or a pointer to an error object?

2019-11-13 Thread Brian Candler
> the current implementation of interfaces is that they always store pointer > values. If you store a non-pointer value in an interface, that value > is copied into memory, and a pointer to that memory is stored in the > interface. I don't understand where you say "that value is copied into memor

Re: [go-nuts] Go gouroutines vs Rust threads

2019-11-13 Thread Russel Winder
On Wed, 2019-11-13 at 06:02 -0800, Serge Hulne wrote: > Am I therefore correct in assuming that, if the problem I am trying to model > is not IO bound or CPU bound, but deals essentially with modeling a large > number of independent cells (a sort of massively parallel « Game of life »), > where eac

[go-nuts] Re: Please make a benchmark of my database on your PC

2019-11-13 Thread Claygod
My new result goos: linux goarch: amd64 pkg: github.com/claygod/coffer BenchmarkClean-8 10 0.00311 ns/op BenchmarkCofferWriteParallel32NotConcurent-8 time="2019-11-13T22:00:13+03:00" level=error msg="open ./test/100031.log: no such file or directoryMethod=workerFollow intera

Re: [go-nuts] pprof cpu profile doesn't write sample to file

2019-11-13 Thread Ian Lance Taylor
On Wed, Nov 13, 2019 at 9:37 AM bln prasad wrote: > > I'm running go application as systemd service. I've enabled cpu profile using > pprof as specified in documents. When service ran, it's creating file but no > samples are getting written to file. > Does it required any special build arguments

Re: [go-nuts] Should I return an error object, or a pointer to an error object?

2019-11-13 Thread Ian Lance Taylor
On Wed, Nov 13, 2019 at 9:24 AM Brian Candler wrote: > > In https://blog.golang.org/error-handling-and-go, it shows the well-known > error interface: > > type error interface { > Error() string > } > > and it gives an example of a user-defined error: > > // errorString is a trivial implementa

[go-nuts] pprof cpu profile doesn't write sample to file

2019-11-13 Thread bln prasad
I'm running go application as systemd service. I've enabled cpu profile using pprof as specified in documents. When service ran, it's creating file but no samples are getting written to file. Does it required any special build arguments? f, err := os.Create("/tmp/cpu.prof") if err

[go-nuts] Should I return an error object, or a pointer to an error object?

2019-11-13 Thread Brian Candler
In https://blog.golang.org/error-handling-and-go, it shows the well-known error interface: type error interface { Error() string } and it gives an example of a user-defined error: // errorString is a trivial implementation of error. type errorString struct { s string } func (e *errorSt

[go-nuts] go.dev is live!

2019-11-13 Thread 'Julie Qiu' via golang-nuts
Hey Gophers, We are excited to share that go.dev, a new hub for Go developers, is now live! At go.dev, you will find information on how to get started with the language, featured use cases, and other resources. It is a companion site to golang.org. You can read about it on the latest Go blog post

Re: [go-nuts] Re: What is the correct way to access/modify slice elements concurrently

2019-11-13 Thread Marvin Renich
* burak serdar [191112 12:45]: > Is there a guarantee that the compiler will not reorganize > instructions around an atomic read/write? That is: > > i++ > k:=atomic.AddInt32(&j,1) > > Is there a guarantee that the compiler won't rewrite this as: > > k:=atomic.AddInt32(&j,1) > i++ First, from o

Re: [go-nuts] Go gouroutines vs Rust threads

2019-11-13 Thread Brian Hatfield
Note: rust also recently landed async/await: https://blog.rust-lang.org/2019/11/07/Async-await-stable.html, though I have not looked into how it schedules the futures (ie, is it a one-cpu loop like swift or node, does it attempt to schedule futures in an M:N fashion like goroutines, etc). It's a re

Re: [go-nuts] Go gouroutines vs Rust threads

2019-11-13 Thread Serge Hulne
Thank you very much for your answers, they are very much appreciated. Serge. -- 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

Re: [go-nuts] Go gouroutines vs Rust threads

2019-11-13 Thread Robert Engels
Also, I find the GC model of Go far simpler that the “borrower” model in Rust - but to each their own. I think the “experts” would say use Rust if it is mission critical or needs to meet absolute performance metrics. > On Nov 13, 2019, at 8:13 AM, Robert Engels wrote: > -- You received t

Re: [go-nuts] Go gouroutines vs Rust threads

2019-11-13 Thread Robert Engels
It may be easier - as you can code it in a more procedural fashion, but you can do it in either system - there are many techniques you can use. There are also “green threads” libraries (crates) available for Rust. These may over more control over the internal scheduler as well. > On Nov 13, 2

Re: [go-nuts] Go gouroutines vs Rust threads

2019-11-13 Thread Serge Hulne
Am I therefore correct in assuming that, if the problem I am trying to model is not IO bound or CPU bound, but deals essentially with modeling a large number of independent cells (a sort of massively parallel « Game of life »), where each cells lives in its own process, it makes more sense to mo

Re: [go-nuts] Go gouroutines vs Rust threads

2019-11-13 Thread Russel Winder
On Wed, 2019-11-13 at 05:14 -0800, Serge Hulne wrote: > Does anybody know if Rust threads are lightweight processes like Go > goroutines or if they rely on system threads (i.e. more like the Python > approach) ? Rust std::thread is all about OS threads. There are many crates dealing with threadpoo

[go-nuts] Go gouroutines vs Rust threads

2019-11-13 Thread Serge Hulne
Does anybody know if Rust threads are lightweight processes like Go goroutines or if they rely on system threads (i.e. more like the Python approach) ? Thanks! -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and

[go-nuts] using or extending or forking+renaming github.com/google/licensecheck to provide similar functionality

2019-11-13 Thread fgergo
Hi, "licensecheck classifies license files and heuristically determines how well they correspond to known open source licenses." I'd like to identify license references in the file system. If I understand correctly package licensecheck in it's current form is not useful to help with this. If it'