[go-nuts] Re: bash completion for flag package

worked like a charm since i understood i needed to source my bashrc! great package here! thanks a lot! On Tuesday, May 23, 2017 at 9:21:07 PM UTC+2, Eyal Posener wrote: > > I recently did the complete package , > that enables bash completion for the go comman

[go-nuts] Re: Go 1.8.3 is released

Chris, When updating Go source to go1.8.3, I encountered this error: ~ $ cd go/src ~/go/src $ git pull remote: Counting objects: 11146, done remote: Finding sources: 100% (528/528) remote: Total 528 (delta 232), reused 503 (delta 232) Receiving objects: 100% (528/528), 682.08 KiB | 505.00 KiB/s,

[go-nuts] Re: Go 1.8.3 is released

Chris, VERSION: <<< HEAD go1.8.1 === go1.8.3 >>> 352996a381701cfa0c16e8de29cbde8f3922182f Peter On Thursday, May 25, 2017 at 9:16:39 AM UTC-4, peterGo wrote: > > Chris, > > When updating Go source to go1.8.3, I encountered this error: > > ~ $ cd go/src > ~/go/src $ git pull > remote

[go-nuts] Re: [golang-dev] Re: Go 1.8.3 is released

Peter, I believe the 1.8 release branch was force-pushed to for 1.8.2, so I don't think you'll be able to git pull and get to 1.8.3. Try a checkout instead, like git checkout go1.8.3. On Thu, May 25, 2017 at 06:24:04 -0700, peterGo wrote: > VERSION: > > <<< HEAD > go1.8.1 > === > go1.8.3

[go-nuts] Problem with HINDI NAMES

package main import (p"fmt" ) func main(){ सोम(1,1,1,21323,2,2,32,1,) } func सोम (num ...int){ var total int for _, r:= range num{ total = total + r } p.Println("तुन्हारा जोड़ है ",total) } DOESN"T WORK But THIS DO

[go-nuts] Problem in Giving Function Name in HINDI ( INDIAN)

Just wanted to let you know that in Hindi we have different symbols for consonant and vowels. If I write a programme with only consonants like - - package main

[go-nuts] DB not releasing connections during performance tests

Hi All, I'm using go-sql-driver/mysql in my web-application. Each API call has about 3-4 queries it performs. Which are all insert or fetch single row queries like: _, err := db.Exec(query, parms) if err != nil { log.Fatal(err) } err := db.QueryRow(query, params).Scan

Re: [go-nuts] Problem with HINDI NAMES

As per the language ref technically this is not a bug as a vowel sign (U+094B 'ो') is a not Unicode letter but practically it is since you the majority of words in Indic languages need them. > On May 24, 2017, at 11:14 PM, Vikram Rawat wrote: > > package main > > import (p"fmt" > > ) > func

Re: [go-nuts] Problem with HINDI NAMES

On Thu, May 25, 2017 at 4:25 PM Vikram Rawat wrote: It's working as specified: https://play.golang.org/p/yviuaufGDQ -- -j -- 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

Re: [go-nuts] Problem with HINDI NAMES

In other words, you should file a bug report (but technically it is a language change). For Go purposes an identifier should start with unicode letter or underscore as now but for the following Unicode chars the rule should be extended to include chars matching Unicode categories space combinin

[go-nuts] Re: Go 1.8.3 is released

The Go1.8.2 and Go 1.8.3 milestones on GitHub are still open. If there's a manual checklist for Go releases, can someone see that closing the GitHub milestone is added to that checklist? On Wednesday, May 24, 2017 at 2:12:52 PM UTC-7, Chris Broadfoot wrote: > > Hi gophers, > > We have just rele

[go-nuts] Re: [golang-dev] Re: Go 1.8.3 is released

Thanks. Fixed. We do have a list (internally, since it involves internal steps to sign the installers using Google's signing infrastructure), so I'll make sure this is on it. On Thu, May 25, 2017 at 10:20 AM, wrote: > The Go1.8.2 and Go 1.8.3 milestones on GitHub are still open. If there's a >

Re: [go-nuts] Problem with HINDI NAMES

This is https://github.com/golang/go/issues/5167. See also https://github.com/golang/go/issues/16033. -rob On Fri, May 26, 2017 at 1:15 AM, Bakul Shah wrote: > In other words, you should file a bug report (but technically it is a > language change). > > For Go purposes an identifier should st

Re: [go-nuts] Problem with HINDI NAMES

In my view, in the "worse is better" unix tradition, you can leave "canonicalization" out. Let the user worry about that (different ways of representing such chars can be checked and warned about by a lint program). Then the compiler only need to allow additional runes that pass unicode.IsMark(

Re: [go-nuts] Problem with HINDI NAMES

Hello Bakul, I am just an R programmer(by which i mean i don't understand programming much). I was looking for an alternative way to python. I really don't understand what you said but i want to let you all know one thing. English hasonly 26 characters but those are not sufficient for languages l

Re: [go-nuts] Problem with HINDI NAMES

The Go team knows this a problem (see the issues listed by Rob Pike). The difficultly in fixing it is that the ecosystem surrounding Go relies on the current definition for identifiers. There is no way to add the characters you need without breaking other tools like syntax highlighters. It is a