Re: [go-nuts] Go Fonts: request for feedback

There are several characteristics of a typeface, which only a typeface designer can truly understand (unless I'm mistaken if you're one). In particular, the non-uniform ascenders, crossbar and apex of humanistic style give the font it's weird typical classic shape. Most people would know about

Re: [go-nuts] About 64bits alignment

On Sat, Feb 4, 2017 at 5:49 AM, T L wrote: > On Saturday, February 4, 2017 at 11:03:11 AM UTC+8, Matt Harden wrote: >> >> Never mind; I just realized that a WaitGroup is not necessarily at the >> start of an allocation or global variable. >> > > Not very get it. > Do you

Re: [go-nuts] Go Fonts: request for feedback

I think the original asked for what exactly is bugging you about the font, not a general statement that somebody somewhere doesn't like it with a link to a broad discussion on the subject of programming fonts. Do you have anything that bothers you about them, maybe in relationship with the list of

Re: [go-nuts] Go Fonts: request for feedback

This is a nice initiative. But the font doesn't look great compared to what we already have in the OSS toolbelt, e.g. Roboto, Inconsolata, Fira, Open Sans, Office Code, etc. I was hoping for something more extravagant. Like most people on Hacker

Re: [go-nuts] About 64bits alignment

https://play.golang.org/p/VWysBwbPCu The above program prints 64-bit aligned addresses on the playground, but that's a 64 bit platform (with 32 bit pointers). On a 32 bit platform x.j is not guaranteed to be 64-bit aligned. The same would be true if we substituted a WaitGroup for int64 in that

Re: [go-nuts] About 64bits alignment

On Saturday, February 4, 2017 at 11:03:11 AM UTC+8, Matt Harden wrote: > > Never mind; I just realized that a WaitGroup is not necessarily at the > start of an allocation or global variable. > Not very get it. Do you mean WaitGroup will be embedded in other types? So we can't use the 64bit

Re: [go-nuts] Re: Google Grumpy (Python->Go)

The compiler cannot yet run under Grumpy because it uses standard libraries that aren't yet supported. The most substantial unsupported library is the ast module. Once https://github.com/google/grumpy/pull/216 is merged, I think we'll be very close to hosting the compiler in Grumpy. At that point,

Re: [go-nuts] About 64bits alignment

Never mind; I just realized that a WaitGroup is not necessarily at the start of an allocation or global variable. On Fri, Feb 3, 2017 at 7:01 PM Matt Harden wrote: > Doesn't the statement "32-bit compilers to not ensure [64 bit alignment at > the start of an allocation]"

Re: [go-nuts] About 64bits alignment

Doesn't the statement "32-bit compilers to not ensure [64 bit alignment at the start of an allocation]" contradict the sync/atomic statement "The first word in a global variable or in an allocated struct or slice can be relied upon to be 64-bit aligned."? On Fri, Feb 3, 2017 at 6:44 AM Ian Lance

[go-nuts] looking for example of CloseRead in production code

Does anyone have a pointer to production code that uses CloseRead or CloseWrite (TCPConn or UnixConn)? I am aware of the net/http test cases. Thanks, -Skip -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop

Re: [go-nuts] Go Fonts: request for feedback

Perhaps a slightly esoteric request: I'd love to see the fonts made available in Plan 9 (acme compatible) font format. I tried doing the conversion and all bar one font size looked terrible. I've gone with that size and am really enjoying being able to distinguish my els from my pipes, but it

[go-nuts] Go Fonts: request for feedback

the font is great. i wondered whether it is possible to add a sans monospaced font. some wierd guy like me myself prefer sans to sans-serif and serif. thanks -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and

Re: [go-nuts] Blabk values when trying to pass a slice to a struct field

Your post gives a lot of clarity on key concepts. The example where you make use of the nil value of an uninitialized slice within a struct is a really good one. Thanks so much! On Fri, Feb 3, 2017 at 6:30 PM, Konstantin Khomoutov < flatw...@users.sourceforge.net> wrote: > On Fri, 3 Feb 2017

[go-nuts] Re: Change to https://golang.org/doc/install

If you read the git history of the installation page you'll see we've pushed the GOROOT instruction lower and lower in the page. However the advice to set GOROOT has permeated to the Go zeitgeist and continues to be promulgated in tutorials and blog posts. On Saturday, 4 February 2017 00:26:46

Re: [go-nuts] talks.golang.org down?

Working for me from New Jersey and California, USA. -- 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,

[go-nuts] talks.golang.org down?

Try to access https://talks.golang.org/ Error: Server ErrorThe service you requested is not available yet. Please try again in 30 seconds. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails

[go-nuts] Re: Google Grumpy (Python->Go)

just been taking a look, and wondered why i couldn't "go get" it, then i see the compiler is in python. which leads to the question; has anyone attempted to compile the compiler to go? On Wednesday, 4 January 2017 19:27:10 UTC, Shawn Milochik wrote: > > I'm surprised this hasn't hit this

Re: [go-nuts] Go Fonts: request for feedback

I would just like to say as a user, the fonts are great and i appreciate that they are continuing to work on them at all. Thanks B! On Feb 2, 2017 7:25 PM, "Nigel Tao" wrote: Bigelow & Holmes, the designers of the Go Fonts, are preparing an update to those fonts. The

Re: [go-nuts] Go Fonts: request for feedback

hi, On Fri, Feb 3, 2017 at 1:25 AM, Nigel Tao wrote: > Bigelow & Holmes, the designers of the Go Fonts, are preparing an > update to those fonts. The changes so far are: > > • adjusted box/chart/shade/split-integral to align vertically > • adjusted shade characters to align

[go-nuts] Re: Go Fonts: request for feedback

Hi Nigel, Is it possible to have the complete set of superscript numerals? Currently the font only has 1,2 & 3 (U+00B9, U+00B2 & U+00B3) available. Regards, On Friday, 3 February 2017 00:25:42 UTC, Nigel Tao wrote: > > Bigelow & Holmes, the designers of the Go Fonts, are preparing an > update

Re: [go-nuts] Re: is it possible to speed up type assertion?

Nothing wrong with micro benchmarks. Sorry if I gave that impression. The problem is in trying to use them to anticipate behavior of a larger system. If you have a "micro question" then a "micro benchmark" is a great one. Most people have macro questions though, and yet they often start with micro

Re: [go-nuts] Is there a "strings.Clone(string) string" alike function?

This program reports only one allocation per operation, which seems to indicate that your solution is already the right one: https://play.golang.org/p/Fx1EMYKRRd On 1 February 2017 at 09:18, T L wrote: > Sometimes, I want to create a new string which will not share the

Re: [go-nuts] About 64bits alignment

On Fri, Feb 3, 2017 at 5:38 AM, T L wrote: > Why does WaitGroup.state method check 64-bit alignment at run time? > Why not make the state field as the first word of WaitGroup struct? > > // https://golang.org/src/sync/waitgroup.go?s=1857:1892#L20 > > type WaitGroup struct { >

Re: [go-nuts] Change to https://golang.org/doc/install

On Fri, Feb 3, 2017 at 1:08 AM, 'pfitzsimons' via golang-nuts wrote: > I guess the reference to GOROOT can be removed now, is there a reason its > still in the install docs? as Dave say's in a galaxy a long time ago >

Re: [go-nuts] About 64bits alignment

Why does WaitGroup.state method check 64-bit alignment at run time? Why not make the state field as the first word of WaitGroup struct? // https://golang.org/src/sync/waitgroup.go?s=1857:1892#L20 type WaitGroup struct { noCopy noCopy // 64-bit value: high 32 bits are counter,

[go-nuts] Change to https://golang.org/doc/install

I guess the reference to GOROOT can be removed now, is there a reason its still in the install docs? as Dave say's in a galaxy a long time ago https://dave.cheney.net/2013/06/14/you-dont-need-to-set-goroot-really "Installing to a custom location The Go binary distributions assume they will

Re: [go-nuts] Re: XML unmarshal woes

I ended up using the excellent package https://github.com/clbanning/mxj by Charles Banning. Thanks a great bunch it really made my day much easier! tors 2 feb. 2017 kl 15:39 skrev Henrik Johansson : > Ahh fantastic thanks a lot! > > tors 2 feb. 2017 kl 15:11 skrev

Re: [go-nuts] Blabk values when trying to pass a slice to a struct field

On Fri, 3 Feb 2017 17:48:18 +0530 Rejoy Nair wrote: > > > I am trying to pass a slice of data to a struct field . The field > > > has a type of another struct. I get blank values in the output. > > > > > > Here is the code: https://play.golang.org/p/-YZ7UUI--D > > > > > > I 'd

Re: [go-nuts] Blabk values when trying to pass a slice to a struct field

Thanks!. thats what I was looking for. I had tried using the assignment Dt.P = Pr before the unmarshalling of the JSON to the variable pdata and it would not work. On Fri, Feb 3, 2017 at 5:18 PM, Konstantin Khomoutov < flatw...@users.sourceforge.net> wrote: > On Fri, 3 Feb 2017 03:32:00 -0800

Re: [go-nuts] Blabk values when trying to pass a slice to a struct field

On Fri, 3 Feb 2017 03:32:00 -0800 (PST) Rejoy wrote: > I am trying to pass a slice of data to a struct field . The field has > a type of another struct. I get blank values in the output. > > Here is the code: https://play.golang.org/p/-YZ7UUI--D > > I 'd like to understand

[go-nuts] Blabk values when trying to pass a slice to a struct field

Hi, I am trying to pass a slice of data to a struct field . The field has a type of another struct. I get blank values in the output. Here is the code: https://play.golang.org/p/-YZ7UUI--D I 'd like to understand how to pass on the slice data to a struct field. -- You received this message

[go-nuts] Re: Is there a reason go doesn't use the small string optomization

I am moving this discussion to this proposal. Thanks for the pointers(pun intended) https://github.com/golang/go/issues/18894#issuecomment-276900485 On Tuesday, January 31, 2017 at 9:12:24 PM UTC-8, Eliot Hedeman wrote: > > I was writing up a proposal about adding the small string >