[go-nuts] [ANN] aah web framework for Go, v0.8 Released

2017-09-01 Thread Jeevanandam M.
*Website:* https://aahframework.org *Documentation:* https://docs.aahframework.org *Release Notes:* https://docs.aahframework.org/v0.8/release-notes.html Please give it a try aah web framework and share your inputs. Your feedback is very valuable. Thanks. Cheers, Jeeva -- You received this

Re: [go-nuts] new project: pixels to svg

2017-09-01 Thread Nigel Tao
On Sat, Sep 2, 2017 at 12:50 AM, wrote: > Feel free to give me feedback on how I can improve the code or the project > setup, etc. I had a quick look. Some thoughts on style, in no particular order: 0. Run gofmt. Your code mixes tabs and spaces, amongst other issues. Gofmt

[go-nuts] Re: Bytconv where art thou

2017-09-01 Thread Michael Jones
Great! Very kind of you On Fri, Sep 1, 2017 at 11:01 AM, peterGo wrote: > Michael and Sebastien, > > Since my bytconv package is currently private, I'm fixing it up for > publication. I hope to make bytconv available in go get'able form within a > week. I'll let you know

Re: [go-nuts] go1.9: problem with go get

2017-09-01 Thread Andreas Briese
Thx i uninstalled 1.9, reinstalled 1.8.3 and the error persisted. In the turned out, chromeos needed a bootstrap installation (using crew install). all the best Andreas On 1 September 2017 at 02:34, Ian Lance Taylor wrote: > On Thu, Aug 31, 2017 at 12:51 PM, abriese

[go-nuts] Re: Struct overloading method issue

2017-09-01 Thread pierre . curto
Maybe I misunderstood your need, but I would just call the A method directly like below. type A struct{} func (a *A) private() {} func (a *A) Public() { a.private() } type B struct {A} func (b *B) private() { b.A.private() } bi := B{} b.Public() //calls the A.Private Le vendredi 1

[go-nuts] Re: Struct overloading method issue

2017-09-01 Thread BeaT Adrian
I solved it for now using composition and Constructors func NewA() { r := A{} r.private = privateForA } func NewB(){ r := B{} r.private = privateForB } I saw using constructors in a few builtin packages so I guess is ok. On Friday, September 1, 2017 at 5:50:52 PM UTC+3, BeaT Adrian

Re: [go-nuts] Re: "for ... range" over array of structs copies values

2017-09-01 Thread Wojciech S. Czarnecki
On Fri, 1 Sep 2017 07:32:34 -0700 (PDT) mspre...@us.ibm.com wrote: > that a variable is considered _addressable_ and that's all there is to it. > Now, in C and other such languages, there is a critical distinction about > addresses that is relevant: is the address on the stack or on the heap?

Re: [go-nuts] Re: "for ... range" over array of structs copies values

2017-09-01 Thread Ian Lance Taylor
On Fri, Sep 1, 2017 at 7:32 AM, wrote: > > This just bit me. I wonder if the discussion above missed the critical > point. Looking at https://golang.org/ref/spec#Address_operators, I see that > a variable is considered _addressable_ and that's all there is to it. Now, >

[go-nuts] new project: pixels to svg

2017-09-01 Thread baggerone
Based on the feedback I received, I've started a new little go project on Github - https://github.com/Baggerone/gopixels2svg Feel free to give me feedback on how I can improve the code or the project setup, etc. To get a quick idea of how to use it, look at *TestWriteSVGToFile *in

[go-nuts] Re: newbie with go 1.9 troubles

2017-09-01 Thread visaxin
actually, you just remove all old version golang directory and download 1.9 && tar will work for me On Thursday, August 31, 2017 at 6:47:37 AM UTC+8, rob wrote: > > Ubuntu 16.04 amd64 > > I d/l the tar.gz file and followed the instructions to install it to > /usr/local/go and set $PATH,

[go-nuts] Re: "for ... range" over array of structs copies values

2017-09-01 Thread mspreitz
This just bit me. I wonder if the discussion above missed the critical point. Looking at https://golang.org/ref/spec#Address_operators, I see that a variable is considered _addressable_ and that's all there is to it. Now, in C and other such languages, there is a critical distinction about

Re: [go-nuts] Help, using fmt.Sprint

2017-09-01 Thread Sam Whited
On Fri, Sep 1, 2017, at 10:00, Tong Sun wrote: > For normal Go way, should I name the string function `*String*()` or ` > *ToString*()`? If you want your type to satisfy the `fmt.Stringer' interface (https://godoc.org/fmt#Stringer) the method should be named `String'. —Sam -- You received

Re: [go-nuts] Help, using fmt.Sprint

2017-09-01 Thread Shawn Milochik
fmt.Sprint returns a string. You're not assigning it to a variable, so it's "lost." -- 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

[go-nuts] Help, using fmt.Sprint

2017-09-01 Thread Tong Sun
Hi, What's wrong with my usage of `fmt.Sprint` in this code: https://play.golang.org/p/ypzfUF_xXA BTW, For normal Go way, should I name the string function `*String*()` or ` *ToString*()`? Thanks -- You received this message because you are subscribed to the Google Groups "golang-nuts"

[go-nuts] Struct overloading method issue

2017-09-01 Thread BeaT Adrian
Hello, I ran into a strange scenario and I wanted to know if there is a better solution for it type A struct{} func (a *A) private() {} func (a *A) Public() { a.private() } type B struct {A} func (b *B) private() {} bi := B{} b.Public() //calls the A.Private I just want to rewrite a

Re: [go-nuts] english language help

2017-09-01 Thread Wojciech S. Czarnecki
On Thu, 31 Aug 2017 05:49:57 -0700 (PDT) "'Niko Schwarz' via golang-nuts" wrote: > I think it's ok to ask in Russian on this group, too. Бусад хэл дээр дэлгэрэнгүй техникийн яриа хэлэлцээ хийх боломжтой юу? Энэ нь хүлээн зөвшөөрөгдсөн үү? OP төгс богино асуултыг

Re: [go-nuts] Bytconv where art thou

2017-09-01 Thread Peter Waller
On 1 September 2017 at 08:49, Sebastien Binet wrote: > > I'd also be very interested in looking at 'bytconv'. And most probably > should use it in anger :) > I've written my own bytconv.Atoi in two projects where it gave a nice speedup, so +1 to this. -- You received this

[go-nuts] Re: sync.Map for caching

2017-09-01 Thread bep
Thanks, snmed, I was looking at LoadOrStore, but I was assuming that any func would be executed in any case. A more illustrative running sample of your first example: https://play.golang.org/p/vjlVu1GnUQ Thanks again! bep fredag 1. september 2017 08.24.10 UTC+2 skrev snmed følgende: > > Hi

[go-nuts] Re: sync.Map for caching

2017-09-01 Thread snmed
Hi Here are two examples how to achieve it: https://play.golang.org/p/wAtyGMSw6g or https://play.golang.org/p/EZWZUOpuwb First example: In best cases it executes the creator function once and returns always the stored item, in bad cases it executes the creator function multiple times but

Re: [go-nuts] sync.Map for caching

2017-09-01 Thread Henrik Johansson
If you absolutely must make sure you ever create 2 instances of any value in the map then I guess you have to lock. Otherwise you can maybe use map.LoadOrStore? fre 1 sep. 2017 kl 00:18 skrev bep : > sync.Map in Go 1.9 is a little low on examples/doc in the wild,