dep is not part of the toolchain. On Tue, 7 Nov 2017, 08:38 Sotirios Mantziaris, <smantzia...@gmail.com> wrote:
> would it not make sense them to keep dep out of the std toolchain to adapt > faster to changes? > > On Tuesday, November 7, 2017 at 9:31:01 AM UTC+2, Dave Cheney wrote: >> >> If you reported an issue today, Nov 6, you could be waiting nearly 9 >> months to see a fix in the next released version of Go. >> >> A project living outside the standard library has little going against it >> other than you have to compile it yourself. >> >> On Tuesday, 7 November 2017 18:28:09 UTC+11, Sotirios Mantziaris wrote: >>> >>> I do not know if the times you mentioned are indeed that long. >>> If it is true then you actually have a good argument. >>> >>> On Tuesday, November 7, 2017 at 9:20:08 AM UTC+2, Florin Pățan wrote: >>>> >>>> I hope not. Anything that ends up in the toolchain is slow to change >>>> and adapt to user needs. If I have a problem with delve today, I can post >>>> an issue, fix it and get the next version of delve az quick as a few hours. >>>> If it would be in the toolchain it could take up to six months to get it >>>> released. >>>> >>>> On Tue, 7 Nov 2017, 07:04 Sotirios Mantziaris, <smant...@gmail.com> >>>> wrote: >>>> >>>>> Yes i know that, but i wonder if it is time to fully integrate delve >>>>> in the go toolchain and ship it with every release like dep, which exists >>>>> in another repository, but will be fullly integrated into the toolchain >>>>> and >>>>> the releases in some future version. >>>>> >>>>> On Tuesday, November 7, 2017 at 1:38:27 AM UTC+2, Florin Pățan wrote: >>>>>> >>>>>> Delve is the one towards which the community rally since gdb, still, >>>>>> doesn't play nice with goroutines. So, for all intents and purposes, >>>>>> delve >>>>>> is the official debugger and the Go Team and Delve Team do work together >>>>>> to >>>>>> give us a better debugging experience. But sometimes the problems that >>>>>> need >>>>>> to be fixed are just too hard to do so quickly. >>>>> >>>>> -- >>>>> You received this message because you are subscribed to a topic in the >>>>> Google Groups "golang-nuts" group. >>>>> To unsubscribe from this topic, visit >>>>> https://groups.google.com/d/topic/golang-nuts/UY6pvL8qeIw/unsubscribe. >>>>> To unsubscribe from this group and all its topics, 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 a topic in the > Google Groups "golang-nuts" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/golang-nuts/UY6pvL8qeIw/unsubscribe. > To unsubscribe from this group and all its topics, 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.
