On Nov 20, 2018, at 12:52 PM, Pat Farrell wrote:
>
> I know, this is both a FAQ and an unanswerable question. I'm an old
> programmer who has used nearly every editor known to man. I am not a fan of
> whole-universe IDEs, but can use them. I also speak vi/vim pretty fluently.
>
> What editors
On Wednesday, November 21, 2018 at 2:38:42 PM UTC-8, Sun Frank wrote:
>
> Perfect! Thank you so much for your answer and explanation, : )
>
It is, unfortunately, a very common "gotcha". More discussion can be found
here: https://github.com/golang/go/issues/20733
Cheers,
-Sam.
> Best
Thanks! I had run into the limit before, but I had seen it was getting
addressed, I just wasn't sure how. I am not running into any looking now,
just wanted to understand what they changed into as we are planning for the
future with hardware choices. It sounds like the memory limit is removed
If this is important and wasn't fixed in 1.11 or at tip then please file a
bug report with a reproducer at https://github.com/golang/go/issues. An
issue number will result in the Go team investigating.
On Friday, November 16, 2018 at 1:12:58 PM UTC-5, Robert Engels wrote:
>
> This article
>
On Wed, Nov 21, 2018 at 2:09 AM, Jan Mercl <0xj...@gmail.com> wrote:
> On Wed, Nov 21, 2018 at 1:49 AM Ian Lance Taylor wrote:
>
>> I can recreate the error with 1.11.2, but the file compiles
>> with tip. I would guess that this is https://golang.org/issue/28616,
>> which should be fixed in
Perfect! Thank you so much for your answer and explanation, : )
Best Regards
Mail : elitegobli...@gmail.com
Mobile : 0422 118 452
TechBlog : http://elitegoblin.github.io
GitHub: http://github.com/eliteGoblin/
andrey mirtchovski 于2018年11月22日周四 上午9:22写道：
> this is a case of a
this is a case of a variable being reused during a range loop.
essentially k[:] is optimized to something resembling (a pointer to
the memory location of the backing array) which is appended as such to
the [][]int variable. the next iteration it is the same variable in
memory, however it's
Hi, just add k := k after the for-range line
--
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
I am using micro editor: https://github.com/zyedidia/micro . It is
terminal-based, supports mouse, uses ctrl+zxcv and shift+arrows for text
manipulation, has a multi cursor feature, syntax highlighting.
Written in golang. Easy to configure and change.
I am using my fork
Hi guys, I came across some code that surprised me, but I could not figured
out why it behave like this,
s := make([][]int, 0)
a1 := [3]int{1, 2, 3}
a2 := [3]int{4, 5, 6}
s = append(s, a1[:])
s = append(s, a2[:])
fmt.Println(s)
mp := make(map[[3]int]bool)
mp[[3]int{1, 2, 3}] = true
mp[[3]int{4,
Thanks! I think programmers are more likely to stay consistent than web
designers — thus this feels a bit better than scraping a web page.
Janne Snabb
sn...@epipe.com
On 20/11/2018 22.06, Caleb Mingle wrote:
Perhaps something built using these may work (sorting the go1* tags
descending?):
Thanks!
This is so helpful. I got an idea. Now I can get integer congressional id :)
ср, 21 нояб. 2018 г. в 12:14, Caleb Mingle :
> I'm not entirely clear on what you're after, but does this help?
> https://play.golang.org/p/AcNBcUVtXGg
>
> That will return you the name field given a state
I'm not entirely clear on what you're after, but does this help?
https://play.golang.org/p/AcNBcUVtXGg
That will return you the name field given a state name. If you need an
integer congressional district number, that will require some modification.
If you want this to work without having to
Hi, I have the same problem, but I just want to scan my custom packages,
when I do the go list. / ... it returns the correct routes, but with the
underscore at the beginning of the routes, it is worth noting that the
project does not have it inside the $ GOPATH (my $ GOPATH is in $ HOME / go)
> People keep adding stuffs into Go and later find themselves unable to
remove existing features due to the backward compatibility promise. Go 1.11
is a different beast than Go 1.0, and is significantly more complex.
For what it's worth, I don't believe that tooling is covered under
the backward
> There is hub [1]. If you have not heard it, its work by
> repo-branch-commits,
Thanks, but as I understand it, this tool is branch-based.
I want to make my workflow oriented around single commits (on a local branch).
Paul
--
You received this message because you are subscribed to the
On Wed, 21 Nov 2018 13:49:32 +
Paul Jolly wrote:
>
> What I'm ultimately trying to achieve is something akin to Gerrit's
> relation chain. That is, have a number of commits on a local branch,
> and have each commit correspond to a GitHub PR. Would involve creating
> some PR-specific
Hi all,
Has anyone thought about/tried to get
https://godoc.org/golang.org/x/review/git-codereview working with a
GitHub backend?
What I'm ultimately trying to achieve is something akin to Gerrit's
relation chain. That is, have a number of commits on a local branch,
and have each commit
> > To add to the responses below, a Language Server Protocol (LSP -
> > https://microsoft.github.io/language-server-protocol/) implementation
> > is also in the works
>
> Is there a link to share wrt 'in the works'?
Sorry, yes, that was needlessly vague.
We get updates from the Go tooling team
thanks，you are right, i got it at that night.
在 2018年11月9日星期五 UTC+8下午10:14:14，Burak Serdar写道：
>
> On Fri, Nov 9, 2018 at 6:35 AM > wrote:
> >
> > front-end info
> > //body struct
> > type Bucket struct {
> >Name string `json:"name"`
> >KeyId string `json:"key_id"`
> >
On Wed, Nov 21, 2018 at 11:58 AM Paul Jolly wrote:
> To add to the responses below, a Language Server Protocol (LSP -
> https://microsoft.github.io/language-server-protocol/) implementation
> is also in the works
Is there a link to share wrt 'in the works'?
--
-j
--
You received this
To add to the responses below, a Language Server Protocol (LSP -
https://microsoft.github.io/language-server-protocol/) implementation
is also in the works that will help to "level the playing field" for
language awareness between editors.
It will also make it possible to easily integrate new
On Wed, Nov 21, 2018 at 1:49 AM Ian Lance Taylor wrote:
> I can recreate the error with 1.11.2, but the file compiles
> with tip. I would guess that this is https://golang.org/issue/28616,
> which should be fixed in 1.11.3.
Thank you. I failed to find that issue. Glad to hear it's fixed
We use GoLand at our company. I used vim with plugins, but Goland is far
superior when it comes to refactoring.
Le mar. 20 nov. 2018 à 21:52, Pat Farrell a écrit :
> I know, this is both a FAQ and an unanswerable question. I'm an old
> programmer who has used nearly every editor known to man. I
24 matches
Mail list logo
