Live data from Hacker News

Visual Studio Code for Go

github.com

221–223 of 223 posts

Re: Visual Studio Code for Go

#221
post #104

Maintainer of the extension here. Happy to answer any questions about VS Code or the Go support specifically.

How does it play with things like glide, gb, and godeps?

I don't think it does. I'm trying to find flags or anything to make it know what gb is. In the gopath, things just work. In a gb project it just says "no buildable files" because it doesn't know to do `gb build`. Tried some other projects like atocker but then they don't seem to play nice with docker-machine.

Re: Visual Studio Code for Go

#222

Maintainer of the extension here. Happy to answer any questions about VS Code or the Go support specifically.

Hi there! I'm giving the Go plugin (latest) for VS Code (latest) a try but I'm not being able to rename code occurrences. "Cannot rename due to errors: Error: Command failed /foo/go/bin/gorename -offset /Users/foo/go/src/github.com/foo/hello/hello.go:#79 -to helloNurse" "rename: -offset \"/Users/foo/go/src/github.com/foo/hello/hello.go:#79\": no identifier at this position" Do I have to do anything specific for it to…

Just in case anyone else got stuck in same matter, I got a reply here https://github.com/Microsoft/vscode-go/issues/165#issuecomme....

Re: Visual Studio Code for Go

#223

Earlier quoted context omitted.

> It's also potentially faster and more efficient than goroutines, because it packs the state to be shared on context switches into what is typically a very tight structure instead of saving the entire stack. A context switch to another goroutine doesn't need to "save the entire stack". The stack is already there. The runtime just needs to keep a pointer to the stack of the suspended goroutine. And the stack is usual…

You have to keep the stack around in memory, as opposed to having a fixed structure. And fixed structures really pull away when you think about allocation: you can use a segregated fit/free list structure, whereas you can't with a variable sized thing like a stack. If the stack starts small and grows, you're paying the costs of copying and reallocation whenever it does: another loss. Allocation in a segregated fit sc…

"Why Events Are A Bad Idea (for high-concurrency servers)" is an interesting counter:

https://www.usenix.org/legacy/events/hotos03/tech/full_paper...

Post reply on HN