Re: [go-nuts] Problem with HINDI NAMES

[Nathan Kerr]

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 socioeconomic problem than a technical one. The next time it can be fixed 
in Go is for Go 2.0 and is already on the list of issues to be considered.

If your main goal is to write programs in your language, you might consider 
using one from 
https://en.wikipedia.org/wiki/Non-English-based_programming_languages

On Friday, May 26, 2017 at 3:26:08 AM UTC+2, Vikram Rawat wrote:
>
> 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 
> like hindi, bengali, gurumukhi, malyalam and many other phonetic languages. 
> So we use entire keyboard to type letters.
>
> In the above example सोम is a proper word with a meaning we just simply 
> can't ignore ो or letters like that at all.
>
> Please tell me what to do. I really want to write program in my language 
> because there arenone written yet.
>
> Thanks for any reply you give me
>
> Regards from India,
>
> Vikram singh Rawat
>
>
> On 26-May-2017 5:44 am, "Bakul Shah" > 
> wrote:
>
> 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() for all but the first rune of an identifier. [Would be 
> nice if we didn't have to wait for the mythical 2.0 for this!]
>
> As for exporting symbols, prepending _ for making symbols private means 
> most likely more symbols will get accidentally exported. Once leaked they 
> are harder to unleak! The default should be to keep things private. Why not 
> instead allow an explicit "export" section?
>
> On May 25, 2017, at 12:37 PM, Rob Pike > 
> wrote:
>
> 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 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 combining (Mc) 
>> and nonspacing (Mn) mark.
>>
>> On May 25, 2017, at 7:47 AM, Bakul Shah > > wrote:
>>
>> 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 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)
>> }
>>
>> -- 
>> 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...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>> -- 
>> 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...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>

-- 
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, visit https://groups.google.com/d/optout.

Re: [go-nuts] Problem with HINDI NAMES

[Vikram Rawat]

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
like hindi, bengali, gurumukhi, malyalam and many other phonetic languages.
So we use entire keyboard to type letters.

In the above example सोम is a proper word with a meaning we just simply
can't ignore ो or letters like that at all.

Please tell me what to do. I really want to write program in my language
because there arenone written yet.

Thanks for any reply you give me

Regards from India,

Vikram singh Rawat


On 26-May-2017 5:44 am, "Bakul Shah"  wrote:

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() for all but the first rune of an identifier. [Would be
nice if we didn't have to wait for the mythical 2.0 for this!]

As for exporting symbols, prepending _ for making symbols private means
most likely more symbols will get accidentally exported. Once leaked they
are harder to unleak! The default should be to keep things private. Why not
instead allow an explicit "export" section?

On May 25, 2017, at 12:37 PM, Rob Pike  wrote:

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 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 combining (Mc)
> and nonspacing (Mn) mark.
>
> On May 25, 2017, at 7:47 AM, Bakul Shah  wrote:
>
> 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 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)
> }
>
> --
> 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, visit https://groups.google.com/d/optout.
>
> --
> 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, visit https://groups.google.com/d/optout.
>

-- 
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, visit https://groups.google.com/d/optout.

Re: [go-nuts] Problem with HINDI NAMES

[Bakul Shah]

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() for all but the first rune of an identifier. [Would be nice if 
we didn't have to wait for the mythical 2.0 for this!]

As for exporting symbols, prepending _ for making symbols private means most 
likely more symbols will get accidentally exported. Once leaked they are harder 
to unleak! The default should be to keep things private. Why not instead allow 
an explicit "export" section?

> On May 25, 2017, at 12:37 PM, Rob Pike  wrote:
> 
> 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 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 combining (Mc) and 
>> nonspacing (Mn) mark.
>> 
>>> On May 25, 2017, at 7:47 AM, Bakul Shah  wrote:
>>> 
>>> 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 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)
 }
>>> -- 
>>> 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, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> 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, visit https://groups.google.com/d/optout.
> 

-- 
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, visit https://groups.google.com/d/optout.

Re: [go-nuts] Problem with HINDI NAMES

[Rob Pike]

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 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 combining (Mc)
> and nonspacing (Mn) mark.
>
> On May 25, 2017, at 7:47 AM, Bakul Shah  wrote:
>
> 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 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)
> }
>
> --
> 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, visit https://groups.google.com/d/optout.
>
> --
> 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, visit https://groups.google.com/d/optout.
>

-- 
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, visit https://groups.google.com/d/optout.

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

[Brad Fitzpatrick]

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
> 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 released Go version 1.8.3, a minor point release.
>>
>> This release includes fixes to the compiler, runtime, documentation, and
>> the
>> database/sql package.
>> https://golang.org/doc/devel/release.html#go1.8.minor
>>
>> It also includes the security fix to the crypto/elliptic package from Go
>> 1.8.2.
>>
>> You can download binary and source distributions from the Go web site:
>> https://golang.org/dl/
>>
>> To compile from source using a Git clone, update to the release with "git
>> checkout go1.8.3" and build as usual.
>>
>> Thanks to everyone who contributed to the release.
>>
>> Chris
>>
> --
> You received this message because you are subscribed to the Google Groups
> "golang-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-dev+unsubscr...@googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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, visit https://groups.google.com/d/optout.

[go-nuts] Re: Go 1.8.3 is released

[mark]

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 released Go version 1.8.3, a minor point release.
>
> This release includes fixes to the compiler, runtime, documentation, and 
> the
> database/sql package.
> https://golang.org/doc/devel/release.html#go1.8.minor
>
> It also includes the security fix to the crypto/elliptic package from Go 
> 1.8.2.
>
> You can download binary and source distributions from the Go web site:
> https://golang.org/dl/
>
> To compile from source using a Git clone, update to the release with "git 
> checkout go1.8.3" and build as usual.
>
> Thanks to everyone who contributed to the release.
>
> Chris
>

-- 
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, visit https://groups.google.com/d/optout.

Re: [go-nuts] Problem with HINDI NAMES

[Bakul Shah]

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 combining (Mc) and nonspacing (Mn) mark.

> On May 25, 2017, at 7:47 AM, Bakul Shah  wrote:
> 
> 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 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)
>> }
> -- 
> 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, visit https://groups.google.com/d/optout.

-- 
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, visit https://groups.google.com/d/optout.

Re: [go-nuts] Problem with HINDI NAMES

[Jan Mercl]

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 an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Problem with HINDI NAMES

[Bakul Shah]

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 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)
> }

-- 
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, visit https://groups.google.com/d/optout.

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

[viridian . reg]

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(&data)
if err != nil {
log.Fatal(err)

}

I have also the following configuration
db.SetMaxOpenConns(50)
db.SetMaxIdleConns(20)

I am making a call to 2 api's which have a combined db call of 8 queires. 
 When I make a call with 120 concurrent users with a ramp up time of 5 sec 
i get Error 1040: Too many connections.

it works fine for up to 90-100 users. My question is why does the db not 
re-using the connections or why does it not release the connections soon 
enough?

As both Exec and QueryRow are supposed to release connections immediately 
since I use Scan soon after, shouldn't the number of connections it support 
be more in number than just double?

Any insight is appreciated.





-- 
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, visit https://groups.google.com/d/optout.

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

[vikramrawat18]

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

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)
}


-

-


it works Fine


But If I add vowel to make it an understandable word. The code breaks...


-

-

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)
}


-

-


it gives me this error.

# command-line-arguments .\Try.go:7: invalid identifier character U+094B 
'ो' .\Try.go:12: invalid identifier character U+094B 'ो'

-

-

however it is necessary to handle it because we can't make a proper word 
without consonant...

Kindly Use a Person who understands the language so to know what is the 
problem...

-

-


And thanks for a wonderful language now all it needs is a data handling library 
like panda or data.table cause entire world is moving towards data science


but overall nice work thanks.


do reply

-- 
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, visit https://groups.google.com/d/optout.

[go-nuts] Problem with HINDI NAMES

[Vikram Rawat]

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 DOES











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)
}

-- 
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, visit https://groups.google.com/d/optout.

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

[Daniel Martí]

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
> >>> 352996a381701cfa0c16e8de29cbde8f3922182f
> 
> Peter

-- 
Daniel Martí - mv...@mvdan.cc - https://mvdan.cc/

-- 
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, visit https://groups.google.com/d/optout.

[go-nuts] Re: Go 1.8.3 is released

[peterGo]

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: 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, done.
> Resolving deltas: 100% (232/232), completed with 101 local objects.
> From https://go.googlesource.com/go
>8babce2..352996a  release-branch.go1.8 -> origin/release-branch.go1.8
>366bb67..a9d8d4d  master -> origin/master
>753452f..2b7a7b7  release-branch.go1.7 -> origin/release-branch.go1.7
>  * [new tag] go1.7.6-> go1.7.6
>  * [new tag] go1.8.3-> go1.8.3
>  * [new tag] go1.8.2-> go1.8.2
> Auto-merging VERSION
> CONFLICT (content): Merge conflict in VERSION
> Automatic merge failed; fix conflicts and then commit the result.
> ~/go/src $ git branch
> * release-branch.go1.8
> $ date
> Thu May 25 09:15:18 EDT 2017
> ~/go/src $ 
>
> Peter
>
> On Wednesday, May 24, 2017 at 5:12:52 PM UTC-4, Chris Broadfoot wrote:
>>
>> Hi gophers,
>>
>> We have just released Go version 1.8.3, a minor point release.
>>
>> This release includes fixes to the compiler, runtime, documentation, and 
>> the
>> database/sql package.
>> https://golang.org/doc/devel/release.html#go1.8.minor
>>
>> It also includes the security fix to the crypto/elliptic package from Go 
>> 1.8.2.
>>
>> You can download binary and source distributions from the Go web site:
>> https://golang.org/dl/
>>
>> To compile from source using a Git clone, update to the release with "git 
>> checkout go1.8.3" and build as usual.
>>
>> Thanks to everyone who contributed to the release.
>>
>> Chris
>>
>

-- 
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, visit https://groups.google.com/d/optout.

[go-nuts] Re: Go 1.8.3 is released

[peterGo]

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, done.
Resolving deltas: 100% (232/232), completed with 101 local objects.
>From https://go.googlesource.com/go
   8babce2..352996a  release-branch.go1.8 -> origin/release-branch.go1.8
   366bb67..a9d8d4d  master -> origin/master
   753452f..2b7a7b7  release-branch.go1.7 -> origin/release-branch.go1.7
 * [new tag] go1.7.6-> go1.7.6
 * [new tag] go1.8.3-> go1.8.3
 * [new tag] go1.8.2-> go1.8.2
Auto-merging VERSION
CONFLICT (content): Merge conflict in VERSION
Automatic merge failed; fix conflicts and then commit the result.
~/go/src $ git branch
* release-branch.go1.8
$ date
Thu May 25 09:15:18 EDT 2017
~/go/src $ 

Peter

On Wednesday, May 24, 2017 at 5:12:52 PM UTC-4, Chris Broadfoot wrote:
>
> Hi gophers,
>
> We have just released Go version 1.8.3, a minor point release.
>
> This release includes fixes to the compiler, runtime, documentation, and 
> the
> database/sql package.
> https://golang.org/doc/devel/release.html#go1.8.minor
>
> It also includes the security fix to the crypto/elliptic package from Go 
> 1.8.2.
>
> You can download binary and source distributions from the Go web site:
> https://golang.org/dl/
>
> To compile from source using a Git clone, update to the release with "git 
> checkout go1.8.3" and build as usual.
>
> Thanks to everyone who contributed to the release.
>
> Chris
>

-- 
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, visit https://groups.google.com/d/optout.

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

[mhhcbon]

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 command line.
> I came to be really satisfied with the result, but the package downside is 
> that the completion can be inconsistent with the actual flags provided by 
> the program.
> I thought how is it possible to add support to the standard library flag 
> package for automatic bash completion, more or less in the same way. 
> (Including installation, and that the program binary will provide bash 
> completion for itself)
>
> Here is what I came out with: https://github.com/posener/flag.
>
> It is 100% interchangeable with the standard library flag package.
> The implementation is also interesting, I only add to make 
> 'flat.Flag.Value' implement an interface I called 'Completer'. All the 
> standard library flags, which do not implement this interface don't 
> complete anything (which is fine) and additional flag types can complete 
> all sort of stuff.
>
> Please let me know your opinion about it.
>
> Cheers,
> Eyal
>

-- 
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, visit https://groups.google.com/d/optout.