[go-nuts] Go += Package Versioning

Hi everyone, I have a new blog post you might be interested in. https://research.swtch.com/vgo. I'll try to watch this thread to answer any questions. Best, Russ -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group an

Re: [go-nuts] Re: Go += Package Versioning

On Tue, Feb 20, 2018 at 1:17 PM, Zellyn wrote: > A couple of initial questions: > >- The "pretend you're importing github.com/foo/bar but actually pull >it from localgit.host/foo/bar" functionality of dep was going to really >simplify things for us. I can't quite tell whether vgo incl

Re: [go-nuts] Go += Package Versioning

On Tue, Feb 20, 2018 at 1:55 PM, David Anderson wrote: > I love this. I want it now. > go get -u golang.org/x/vgo :-) I've struggled with `glide` and `dep` dependency hell a lot in my Go > projects (especially those that use the Kubernetes client library, which > abuses "I, the library author,

Re: [go-nuts] Go += Package Versioning

On Tue, Feb 20, 2018 at 2:35 PM, Devon H. O'Dell wrote: > With regards to minimum version selection, if I depend on some feature > present, this comes with two implicit dependencies: correctness and > safety. My knee-jerk reaction here is that the time folks spend > "telling the package manager,

Re: [go-nuts] Go += Package Versioning

On Tue, Feb 20, 2018 at 3:46 PM, Bakul Shah wrote: > May be one can write a tool around or similar to "vgo test" to > test and update not to the latest but some earlier version. > For example, if pkg A currently imports C v1.x and B imports C > v1.y, through iterative testing one may find C v1.z

Re: [go-nuts] Go += Package Versioning

For people who haven't seen it yet: research.swtch.com/vgo-import is the post Sam's referring to. On Wed, Feb 21, 2018 at 2:22 PM, Sam Whited wrote: > Something that is still unclear to me even after reading todays post is > how I would manage the various package import paths created by the impo

[go-nuts] Re: [golang-dev] Go += Package Versioning

> [+cc golang-nuts, it was lost at some point] BCC golang-nuts. Please do NOT mix the two threads. I expect that the two different lists with different people will have different focuses for their discussions. On Wed, Feb 21, 2018 at 5:31 PM, Aram Hăvărneanu wrote: > [+cc golang-nuts, it was l

Re: [go-nuts] Go += Package Versioning

Replying to this thread to drop golang-dev. Please try to keep the two threads separate. I should not have used the same subject for each. Sorry. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving em

Re: [go-nuts] Go += Package Versioning

On Tue, Feb 20, 2018 at 4:07 PM, David Anderson wrote: > On Tue, Feb 20, 2018 at 11:37 AM, Russ Cox wrote: > >> On Tue, Feb 20, 2018 at 1:55 PM, David Anderson wrote: >> >>> I love this. I want it now. >>> >> >> go get -u golang.org/x/vg

Re: [go-nuts] Go += Package Versioning

On Tue, Feb 20, 2018 at 5:14 PM, Dave MacFarlane wrote: > I really like this, except for the claim that it the blog post that it > will eliminate vendoring and deprecate GOPATH and the problems that > will cause for backwards compatibility for things that are currently > using them. If this is go

[go-nuts] do you use binary-only packages?

The go command supports "binary-only packages", in which the compiled .a file is installed in GOROOT/pkg or GOPATH/pkg but the corresponding source code is only a stub with relevant imports (for linking), a special comment marking it as a binary-only package, and perhaps documentation for exported

Re: [go-nuts] goimports performance degrades in go module

On Wed, Nov 7, 2018 at 7:43 PM Joseph Lorenzini wrote: > If have a go.mod, goimports takes 30 seconds to run. If I remove the > go.mod, then goimports takes half a second to run. Is this expected? Is > goimports trying to do something with the packages found in go.mod? Is > there a way to configu

Re: [go-nuts] Best practices for internal repository management

On Fri, Sep 22, 2017 at 1:08 PM, wrote: > Hi all, > > I have a question regarding modern best practices for go repositories. As > we are building out services in go, we still have the opportunity now to > refactor the service code pretty dynamically. So now is a good time to > check and see if we

Re: [go-nuts] Why so many opt-out changes to test runs in 1.10?

First, a general point. We care very much about getting the default experience right for Go users. These features are opt-in because we believe in both cases that "on" is the right default, that developers will be more productive with these on by default than having to know to opt in. - You shoul

Re: [go-nuts] Re: Go 1.10 Beta 2 is released

See also https://github.com/golang/go/issues/7381 especially https://github.com/golang/go/issues/7381#issuecomment-66091683. Russ On Thu, Jan 18, 2018 at 5:21 AM, Dave Cheney wrote: > I am running the same version and do not see that errro. Have you modified > your ulimit? Does your machine ha

[go-nuts] Re: [golang-dev] Try our new module mirror!

On Tue, Apr 30, 2019 at 5:07 AM Jakub Cajka wrote: > > Our privacy policy explains how we collect and use your information. The > > privacy policy for all of these services is proxy.golang.org/privacy. > > if I'm not mistaken the page that you are linking for privacy information > of the proxy se

Re: [go-nuts] Interesting public commentary on Go...

On Mon, May 27, 2019 at 7:08 PM Matt Farina wrote: > 1) when a company runs a project without much publicly documented process > but does as they choose, isn't that a sign of a company run project? > 2) The go team at Google has had processes that are not public. One > example is the proposal rev

Re: [go-nuts] Interesting public commentary on Go...

On Tue, May 28, 2019 at 12:46 PM Matt Farina wrote: > Let me be a little more clear. In the docs (see the version prior to the > 2018 update at > https://github.com/golang/proposal/tree/a16a937b3b39c4c42f063842407c30c4c451b524#process) > there was no documentation on the proposal reviewers on the

Re: [go-nuts] Interesting public commentary on Go...

Hi all, I spent a while trying to work out what I want to say about the general theme of Go and open source, but in the end I realized that my talk at Gophercon 2015 is a better articulation of what open source means for Go, and what Google's role is, than any email I can write in a few hours toda

[go-nuts] Re: [golang-dev] Stalking people online for thought crimes! This is what the Go project has succumbed to!

iscussions into one discussion in one place. I picked golang-nuts because that is roughly a superset of golang-dev. To everyone reading, please try to reply to golang-nuts only (not golang-dev), so we can have a single conversation. Thanks very much. Russ On Thu, Oct 27, 2016 at 9:58 AM Russ

Re: [go-nuts] Tooling experience feedback

FWIW 'go help all' is essentially 'go doc go'. On Fri, Oct 21, 2016 at 9:46 AM Mathieu Lonjaret wrote: > As you said, sometimes one is not sure in which X for "go help X" one > might find the information they're looking for. So one can end up > trying several of them before finding the relevant

[go-nuts] Re: [golang-dev] Re: Stalking people online for thought crimes! This is what the Go project has succumbed to!

+golang-nuts bcc golang-dev On Thu, Oct 27, 2016 at 11:58 AM Aram Hăvărneanu wrote: > On Thu, Oct 27, 2016 at 5:36 PM, wrote: > > I do want to emphasize the last line of the email we sent, which does not > > appear in your post here: > > > > Please feel free to reach out if you have any ques

Re: [go-nuts] Re: Stalking people online for thought crimes! This is what the Go project has succumbed to!

On Thu, Oct 27, 2016 at 12:07 PM Pietro Gagliardi wrote: > Did golang-dev stop sending emails? I haven't received anything since > October 16. Or should I contact Google Groups support and/or my email > provider? > golang-dev is still active. I'll look into your subscription and mail you off lis

[go-nuts] Re: [golang-dev] Re: Stalking people online for thought crimes! This is what the Go project has succumbed to!

+golang-nuts bcc golang-dev On Thu, Oct 27, 2016 at 1:30 PM Ugorji wrote: > I understand the sentiment, and why someone might choose to report this. > But I agree with Aram that the response was very heavy-handed and > threatening, especially for what is a very minor and border-line subjective >

[go-nuts] Re: [golang-dev] Re: Stalking people online for thought crimes! This is what the Go project has succumbed to!

+golang-nuts bcc golang-dev On Fri, Oct 28, 2016 at 11:26 PM wrote: > If you don't like the framework just don't use it. > I'm using this framework in production for a long time and the author > makes his best to solve any incoming issue. > > He, literally, gave his personal time and money to se

[go-nuts] anyone using pkg-config on Windows?

We would like to fix the behavior of cgo invoking pkg-config on Windows, for golang.org/issue/16455. From the failure in the report, it appears that pkg-config --libs printed the actual text "C:/Program Files (x86)/libgit2/lib" as part of its output, without any kind of escaping of the spaces in th

[go-nuts] Re: [golang-dev] How to improve the performance of io.Copy during copying data from one TCP connection to another TCP connection

+golang-nuts, bcc golang-dev How did you get the pprof profile? How long did your test run for? pprof has 12 seconds of CPU profile samples (the Total: line). If your test ran for a lot more than 12 seconds (typically a profile is fetched for 30 seconds), then the problem is not the CPU usage. If

[go-nuts] Re: [golang-dev] go version inconsistency with Linux and Windows

[+golang-nuts, bcc golang-dev, per golang.org/wiki/Questions] On Mon, Dec 5, 2016 at 10:24 AM, wrote: > Hello, > I just notice that go version is inconsistency on Linux and Windows. > I have unexpected return carriage on Windows (not on Linux). > I don't know whether you can fix it w/o break the

Re: [go-nuts] Deleting the /r/golang subreddit

Although this conversation started out on the wrong foot, it did end up being a valuable discussion. If you haven't seen the posts yet, the conversation continued on /r/golang. I want to update this thread to point at my latest post there, proposing that the Googlers who are moderators all step bac

Re: [go-nuts] 2016 User Survey Results published

On Mon, Mar 6, 2017 at 12:42 PM, Pablo de la Concepción Sanz < pconcepc...@gmail.com> wrote: > Hi, > > First of all, thanks for collecting and sharing the info. I've noticed > that on some questios, some answers are mostly the same but they are > separate. For instance for "What one addition would

Re: [go-nuts] dep: Roadmap for merging into the toolchain

On Tue, Mar 7, 2017 at 6:47 AM, Sam Boyer wrote: > Hi folks, > > Since we opened up the dep project in > late January, there's been flurry of contributions, which has been great. > However, the plans and end goal of dep haven't been entirely clear to > everyone. >

Re: [go-nuts] dep: Roadmap for merging into the toolchain

On Mon, Mar 13, 2017 at 5:09 PM, Russ Cox wrote: > By far the most important things to do with dep right now are (1) build > something people can use and get benefit from today and eliminate blockers > to adoption and (2) based on experience with that usage, learn what the > eventua

Re: [go-nuts] Seeking new custodian for godoc.org

> [go-nuts] Seeking new custodian for godoc.org The Go team is the custodian for godoc.org and we are not seeking a new one. > Legal advice will apparently force the Go team to close godoc.org [1] This is a grotesque misrepresentation of what I wrote. This is what I wrote: *# Why is there a new

Re: [go-nuts] Re: political fundraising on golang.org!

Hi everyone, I wanted to reply here to acknowledge the feedback on this thread. I hear those of you who are uncomfortable with the banner, and I appreciate the honest and mostly constructive discussion here. As the Rust team said well, tech is and will always be political, not in the sense of pol

Re: [go-nuts] Black Lives Matter question

Sorry, but this thread is definitely off-topic here. I'm going to lock this conversation. Best, Russ On Tue, Jun 16, 2020 at 4:53 PM Jon Perryman wrote: > Sorry for this being a little off topic but unlike the media which thinks > with the heart, programmers tend to think with their head. I wa

[go-nuts] draft design for // +build replacement

Hi all, I've posted a draft design for replacing // +build lines with //go:build lines that support standard boolean expression syntax. It is a draft design I'm circulating for feedback, not an official proposal. (I certainly hope it will be well received and can be made into a proposal, but that'

Re: [go-nuts] draft design for // +build replacement

For what it's worth, I am (unsurprisingly) a big fan of the filename-based constraints. It's a lightweight convention that has served us incredibly well. I really like being able to see in a directory listing which files go with what. It would be unfortunate if we had to put the redundant info insi

Re: [go-nuts] godoc.org pkg.go.dev banner feedback

Thanks for the feedback Jan. Google is on an extended holiday weekend for the US holiday but we'll definitely chase this down when people are back. Best, Russ On Thu, Jul 2, 2020 at 11:38 AM Jan Mercl <0xj...@gmail.com> wrote: > godoc.org displays packages from the domain modernc.org just fine.

Re: [go-nuts] draft design for // +build replacement

On Tue, Jul 7, 2020 at 2:56 AM Amnon wrote: > A sensible, well thought out, design. > > My main worry is that we will come unstack in places that are using > versions of the Go toolchain older than N-2. > Is there any reason for them not to upgrade? No > Should they upgrade? Definitely > But some

[go-nuts] draft designs for file system interfaces & file embedding

Hi all, I've posted two draft designs: one introducing general-purpose file system interfaces, with Rob Pike; and one for embedding files into Go programs, with Brad Fitzpatrick. These are draft designs we're circulating for feedback, not official proposals. (We certainly hope they will be well re

Re: [go-nuts] Generics and parentheses

So it sounds like everyone is in favor of the entire generics proposal and all the semantics, and all we have left to hammer out is the bracket characters? Do I have that right? Best, Russ -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsub

Re: [go-nuts] [ generics] Moving forward with the generics design draft

On Fri, Aug 21, 2020 at 1:30 PM 'Axel Wagner' via golang-nuts < golang-nuts@googlegroups.com> wrote: > My one concern with making it an alias is error messages. > If the source code says "any", I think so should the error messages. > Currently, the compiler forgets aliases too early >

Re: [go-nuts] [ generics] Moving forward with the generics design draft

Hi all, A few people have raised concerns about "encouraging" use of any instead of interface{}, on the grounds that it is not idiomatic Go. I just wanted to acknowledge that yes, it's not idiomatic Go today, but that's true of essentially every language change. Thinking about future usage is a go

Re: [go-nuts] Missing the review meeting notes

Apologies, and thanks for the ping. There was no 2023-09-14 meeting due to the Go quiet week. It looks like I forgot to post the minutes after the 2023-09-20 meeting, which I've just done. There was no 2023-09-27 meeting due to GopherCon. Best, Russ On Mon, Oct 2, 2023 at 7:14 AM p...@morth.org

Re: [go-nuts] rsc.io/script: How to contribute?

Hi all, I published rsc.io/script for people to play with, to support my testing talk . For now it is on a back burner - I get so much GitHub mail that I cannot keep up with all the notifications, so I hadn't seen the activity there. Perhaps at some point we wil

Re: [go-nuts] Re: After Disbanding the Python Team, Google’s Go Team Faces Turmoil: Technical Lead and 12-Year Project Leader Steps Down

Hi all, There is no need for this discussion to get heated. There is also no turmoil, as we've already established. For those who can't see the article due to the Medium paywall, there is a copy here: https://archive.ph/BQj5j. It reads like ChatGPT summarized the sources at the end. If nothing el

Re: [go-nuts] Should I return a value or pointer?

In the very old days, errors.New was spelled os.NewError, and it returned an os.errorString, not an &os.errorString, and so those error implementations did compare by string value. Arranging for the pointer to be used instead was done explicitly so that errors.New called with the same text from mul