Re: [go-nuts] Re: Algorithm Club

On Thursday, 30 March 2017 03:15:33 UTC+3, Will Faught wrote: > > Egon: > > >See > https://docs.google.com/document/d/1vrAy9gMpMoS3uaVphB32uVXX4pi-HnNjkMEgyAHX4N4/edit#heading=h.j8r1gvdb6qg9 > > I don't see the Implicit Boxing section point out that this is what > happens now when you shoehorn ev

RE: [go-nuts] time: error prone implementation of Time.Format

Granted, but is this a common occurrence? Also, the workaround is easy. On the other hand, how common are the errors which would be caught by adding the test? John John Souvestre - New Orleans LA -Original Message- From: golang-nuts@googlegroups.com [mailto:golang-nuts@googlegrou

[go-nuts] how to debug in gomobile? & can gomobile support mac or linux sometime

As too me gomobile now are more like a game engine (for ui is gl) , like cocos2dx. but unlike cocos2dx, it only support mobile, and did not offer a way to debug in wiki. how to debug, if it could not be debug in mobile. at least let it support mac or linux so , so we are easy to debug -- Yo

[go-nuts] New Smallcaps Go Fonts; other Go Fonts updated

Bigelow & Holmes have prepared new versions of the Go Fonts that we released late last year (https://blog.golang.org/go-fonts). The version numbers have changed from 2.004 to 2.008. ChangeLog: * New! 2 new fonts, bringing the total to 12: Go Smallcaps and Go Smallcaps Italic. * New! U+FFFD REPLACE

Re: [go-nuts] Re: Algorithm Club

Egon: >See https://docs.google.com/document/d/1vrAy9gMpMoS3uaVphB32uVXX4pi- HnNjkMEgyAHX4N4/edit#heading=h.j8r1gvdb6qg9 I don't see the Implicit Boxing section point out that this is what happens now when you shoehorn everything into interface{}. In this sense, I don't see a performance downside

[go-nuts] Re: directory name versus package name

I like the idea that the go tool would enforce matching directory and package names. This would help us in case we forget to be consistent... On Wednesday, March 29, 2017 at 5:18:52 PM UTC+10, Dorival Pedroso wrote: > > Hello, > > I haven't noticed that the code below (located at *$GOPATH/src/My

Re: [go-nuts] time: error prone implementation of Time.Format

On Wed, Mar 29, 2017 at 2:29 PM, Manlio Perillo wrote: > Il giorno mercoledì 29 marzo 2017 23:18:09 UTC+2, Ian Lance Taylor ha > scritto: >> >> On Wed, Mar 29, 2017 at 2:03 PM, Manlio Perillo >> wrote: >> > In a program I have a function that formats the time in Italian date >> > format: >> > dd/

Re: [go-nuts] time: error prone implementation of Time.Format

Il giorno mercoledì 29 marzo 2017 23:18:09 UTC+2, Ian Lance Taylor ha scritto: > > On Wed, Mar 29, 2017 at 2:03 PM, Manlio Perillo > > wrote: > > In a program I have a function that formats the time in Italian date > format: > > dd/mm/, but, due to an oversight, I wrote the layout string a

Re: [go-nuts] time: error prone implementation of Time.Format

On Wed, Mar 29, 2017 at 2:03 PM, Manlio Perillo wrote: > In a program I have a function that formats the time in Italian date format: > dd/mm/, but, due to an oversight, I wrote the layout string as > "02/02/2006", instead of "02/01/2006". > This caused all the dates to be incorrectly formatte

[go-nuts] time: error prone implementation of Time.Format

In a program I have a function that formats the time in Italian date format: dd/mm/, but, due to an oversight, I wrote the layout string as "02/02/2006", instead of "02/01/2006". This caused all the dates to be incorrectly formatted. IMHO, this is a nasty behavior. The layout is clearly inc

[go-nuts] [POC] gigo: go generate on steroids!

Hi ! I m very happy to share with you gigo Its a go generate on steroids, Its more close to something like babel than go generate, see, in input it takes type Todo struct { Name string Done bool } type Todos implements { // it reads as a mutexed list of todo. } func (t *Todos) Hello()

[go-nuts] Re: Go build from windows 32bits to linux

> > > > > > > > set goos=linux > set goarch=386

Re: [go-nuts] Syscalls inside loops + runtime.KeepAlive

On Wed, Mar 29, 2017 at 9:42 AM, Caleb Spare wrote: > I have a question about this runtime.KeepAlive call: > > https://github.com/golang/go/blob/041ecb697f0e867a2bb0bf219cc2fd5f77057c2e/src/os/dir_unix.go#L68 > > (There are other examples in the stdlib as well, I think.) > > It seems to me that, s

Re: [go-nuts] Re: Last Gasp Call for Native Decimal Support

> No! We want to use operators like + , - , * and / with decimal values. This is actualy a "No Go" ! -- 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

[go-nuts] Go build from windows 32bits to linux

get an error when execute go build SET GOOS=linux SET GOARCH=386 SET CGO_ENABLED=1 SET CXX=mingw32-g++ SET CC=mingw32-c++ gopkg.in/rana/ora.v3 ..\gopkg.in\rana\ora.v3\conn.go:51: undefined: Env ..\gopkg.in\rana\ora.v3\conn.go:52: undefined: Ses ..\gopkg.in\rana\ora.v3\pool.go:63: undefined: E

[go-nuts] Syscalls inside loops + runtime.KeepAlive

I have a question about this runtime.KeepAlive call: https://github.com/golang/go/blob/041ecb697f0e867a2bb0bf219cc2fd5f77057c2e/src/os/dir_unix.go#L68 (There are other examples in the stdlib as well, I think.) It seems to me that, strictly speaking, KeepAlive is unnecessary here since the compil

[go-nuts] Re: Workspace and dependencies

To add to the previous answer, > I've read that GOPATH is the location of my workspace, where all of my go code belongs (personal project and dependencies of all of these projects). yes (so far) > If I want to push one of my project on github, will I push only my project source code or will I

[go-nuts] Re: Workspace and dependencies

https://blog.gopheracademy.com/advent-2015/vendor-folder/ On Monday, March 27, 2017 at 10:45:51 AM UTC+5:30, Rafo Ufoun wrote: > > Hello everyone ! > > I'm new to golang and I have some questions about the workspace and the > dependencies management. > > I've read that GOPATH is the location of

[go-nuts] Re: directory name versus package name

This is touched upon in this blog post . It is confusing that the import path would not match the package it contains. On Wednesday, March 29, 2017 at 6:18:52 PM UTC+11, Dorival Pedroso wrote: > > Hello, > > I haven't noticed that the code below (loca

Re: [go-nuts] directory name versus package name

On Wed, Mar 29, 2017 at 9:19 AM Dorival Pedroso wrote: > Anyway, so, why using package mylib then? 'mylib' is the implicit qualifier used to access the exported identifiers from that package from within a package importing it. -- -j -- You received this message because you are subscribed to

Re: [go-nuts] Re: Unexpected behavior with panic/defer/recover

There is also one additional caveat (not for your example, but just in case you stumble upon it): recover must be called *from a deferred function, *meaning "defer recover()" won't work either. You *always* need to wrap recover in a function and that function *always* needs to be directly defer'd.

[go-nuts] directory name versus package name

Hello, I haven't noticed that the code below (located at *$GOPATH/src/MyWrapper*): package mylib import "fmt" func SayHello() { fmt.Println("hello") } is actually being installed (go install) as a *MyWrapper* package, even though the package name was explicitly given as *mylib*. I couldn't f