Re: [go-nuts] Go Fonts: Double double copyright notice in gomono.TTF and friends

On Sun, Oct 1, 2017 at 8:50 AM, as wrote: > The official go fonts contain two identical copyright notices inside the TTF > data slice. One in UTF-8 and one in UTF16 format. These make their way into > the final go binary. Bug or intentional TTF standard? Intentional, unfortunately. It's may not b

Re: [go-nuts] [security] Go 1.8.4 and Go 1.9.1 are released

God no, My system is managed by a *package manager* and I want it to stay that way On Thu, Oct 5, 2017, 03:40 Bakul Shah wrote: > Would it make sense for Go to update itself? Something > like "go update " that fetches a platform > specific release, does some basic sanity tests and > if all goes

Re: [go-nuts] [security] Go 1.8.4 and Go 1.9.1 are released

Would it make sense for Go to update itself? Something like "go update " that fetches a platform specific release, does some basic sanity tests and if all goes well, overwrites $GOROOT. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscri

Re: [go-nuts] Memory Safety

On Wed, Oct 4, 2017 at 2:07 PM, John Souvestre wrote: > Thanks for the info. > > I believe that Windows generally requires that user opt-in (set in the exe) > for DEP and ASLR. However, it seems that Go exe's for Windows don't have the > DEP opt-in set. > > Worth opening some issues? Sure. Th

RE: [go-nuts] Memory Safety

Thanks for the info. I believe that Windows generally requires that user opt-in (set in the exe) for DEP and ASLR. However, it seems that Go exe's for Windows don't have the DEP opt-in set. Worth opening some issues? John John Souvestre - New Orleans LA -Original Message- From:

[go-nuts] Re: [security] Go 1.8.4 and Go 1.9.1 are released

I updated my release related resources: - Go Release Timeline - When Should You Upgrade Go? Hope the community finds them useful. Nathan On Wednesday, October 4, 2017 at 10:35:

[go-nuts] [security] Go 1.8.4 and Go 1.9.1 are released

Hi gophers, Two security-related issues were recently reported. To address this issue, we have just released Go 1.8.4 and Go 1.9.1. We recommend that all users update to one of these releases (if you're not sure which, choose Go 1.9.1). The issues addressed by these releases are: By nesting a g

Re: [go-nuts] Memory Safety

On Wed, Oct 4, 2017 at 1:07 PM, John Souvestre wrote: > > Does Go provide Data Execution Prevention (DEP) and Address space layout > randomization (ASLR)? Go does not prevent the operating system from implementing Data Execution Prevention. If the OS implements it, it will apply to Go programs a

[go-nuts] Memory Safety

Does Go provide Data Execution Prevention (DEP) and Address space layout randomization (ASLR)? If not, any reasons why or any plans to implement? Thanks, John John Souvestre - New Orleans LA -- You received this message because you are subscribed to the Google Groups "golang

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

*Website:* https://aahframework.org *Documentation:* https://docs.aahframework.org *Release Notes:* https://docs.aahframework.org/v0.9/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 me

Re: [go-nuts] Re: potential gofmt style inconsistency

On Wed, Oct 4, 2017 at 11:15 AM, rattias via golang-nuts wrote: >> Consider: > > > foo(1+2) > foo(1+2, 3) > > After formatting it becomes > foo(1 + 2) > foo(1+2, 3) > > This might be working as intended, but it's awful. Any chance this might be > reconsidered? At this point, I doubt it. It is in

[go-nuts] Re: potential gofmt style inconsistency

> > Consider: foo(1+2) foo(1+2, 3) After formatting it becomes foo(1 + 2) foo(1+2, 3) This might be working as intended, but it's awful. Any chance this might be reconsidered? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe

Re: [go-nuts] Memory issues when spawning 1 million go routines that communicate on a channel

ok. the short answer is that if you make a few million somethings -- goroutines, channels, whatever -- and they all wait for the first event in order to start, then what is certain is that you'll attain the peak memory usage needed to hold them all at once. it means the OS will have surrendered t

[go-nuts] Re: Announcing: Skylark in Go

This looks super cool, btw. I've been wanting a way to extend go programs, and lua wasn't really doing it for me. Python(ish) is much more comfortable for most people, I'd think. Can't wait to try it out. > -- You received this message because you are subscribed to the Google Groups "golan

Re: [go-nuts] Memory issues when spawning 1 million go routines that communicate on a channel

That's an interesting solution, but what I'm trying to figure out is why the memory usage is this high and understand how go handles this. On Tue, Oct 3, 2017 at 9:16 PM Michael Jones wrote: > Or you could do it this way... > > https://play.golang.org/p/rU2ONi51ec > > On Mon, Oct 2, 2017 at 7:26

Re: [go-nuts] Go get -f still checking VCS

On Wednesday, 4 October 2017 09:44:48 UTC+2, alexandre...@gmail.com wrote: > > I do want it to get all the dependencies (basic HTTP/S fetch). I just > don't want it to worry about Git or any other VCS, since I just downloaded > a snapshot as a tarball. > go get cannot do this directly for you as

Re: [go-nuts] Go get -f still checking VCS

On Tuesday, October 3, 2017 at 11:20:11 AM UTC+2, Jakob Borg wrote: > > On 3 Oct 2017, at 10:17, alexandre...@gmail.com wrote: > > > > Thanks. However, "go get -t" still complains about "missing Git > command". Indeed, on that machine I intentionally don't use any VCS (just > a source tarba