[go-nuts] Re: How to update packages without duplicating distro packages

Hi, I'm using this approach as workaround: for dir in src/github.com/*/* src/golang.org/*/* src/gopkg.in/*; do go get -u $dir; done понедельник, 6 августа 2018 г., 7:12:58 UTC+3 пользователь Kevin Locke написал: > > Hello, > > Is there a way to update packages installed using `go get` witho

[go-nuts] Re: How to update packages without duplicating distro packages

Sorry, this one has correct paths: cd $GOPATH/src && for dir in github.com/*/* golang.org/*/* gopkg.in/*; do echo "go get -u $dir"; done среда, 8 августа 2018 г., 1:30:53 UTC+3 пользователь Space A. написал: > > Hi, > > I'm using this approach as workar

[go-nuts] Re: How to update packages without duplicating distro packages

Hi, I'm using this approach as workaround: cd $GOPATH/src && for dir in github.com/*/* golang.org/*/* gopkg.in/*; do go get -u $dir; done понедельник, 6 августа 2018 г., 7:12:58 UTC+3 пользователь Kevin Locke написал: > > Hello, > > Is there a way to update packages installed using `go get`

Re: [go-nuts] How to update packages without duplicating distro packages

Just wondering, have you noticed my message? I think it's the only possible solution atm. Regards, четверг, 9 августа 2018 г., 1:09:40 UTC+3 пользователь Kevin Locke написал: > > On Wed, 2018-08-08 at 21:57 +, Jakob Borg wrote: > > What’s happening here is that you are pulling in more depen

[go-nuts] Re: golang + wasm three times slower than javascript?

Hi Kim, check this out: https://medium.com/gopherjs/surprises-in-gopherjs-performance-4a0a49b04ecd You will find some comparison of native Go vs C vs GopherJS (and JS itself, in general), with surprisingly "fast" JS* and "slow" Go. However the reason is not that obvious... Regards пятница, 1

Re: [go-nuts] How to signal(sigint) blocking goroutine

> > The first step is to get the idea of signals out of your head. As I > said, you can not send a signal to a goroutine. It's the wrong > approach. > > Instead, create a context.Context value (e.g., context.Background)... > Hmm... *Do not communicate by sharing memory; instead, share memor

Re: [go-nuts] liteide x34.1 released, support go1.11 modules

Thank you for your great work! понедельник, 13 августа 2018 г., 18:01:22 UTC+3 пользователь visualfc написал: > > Hi, all. > LiteIDE X34.1 released! > This version update gocode to support go1.11 modules and vendor by source > parser. > > * LiteIDE Home > > * LiteIDE Sourc

[go-nuts] Re: I am not in favor of generics.

+1 Go doesn't need generics, in fact it goes against its philosophy and core values. Lack of generics was one of the reasons I moved to Go, I worked with Java since version 3, and I do believe that generics just made Java worse. Regards. понедельник, 17 сентября 2018 г., 19:04:26 UTC+3 польз

[go-nuts] Re: gomobile: what's the right way to make widgets?

I wish go2 team would focus on cross-platform GUI rather than nobody-needed generics after all. There is nothing you can do atm, write your own library I guess... пятница, 26 октября 2018 г., 19:48:37 UTC+3 пользователь Andrew Williams написал: > > I'd be very interested to see if it would be p

[go-nuts] Re: Go Performance

You didn't provide any details on the tests. But I think the idea was same as usual - send some "Hello world" over network. If so all these numbers have nothing to do with real world. PS: ofc this doesn't mean that something is more or less performant than the other. понедельник, 29 октября 2

Re: [go-nuts] Correct way to solve slice of interface type problem

it's pointer that implements, so iface[i] = &p среда, 31 октября 2018 г., 3:30:26 UTC+3 пользователь Justin Israel написал: > > > > On Wed, Oct 31, 2018 at 11:21 AM > wrote: > >> Hello, everyone. >> Consider following code: >> >> package main >> import "fmt" >> >> type implementation struct { >>

Re: [go-nuts] Correct way to solve slice of interface type problem

It's already trivial 3 lines o code. Readable, light, and simple. And it's a question tbh, if topic starter even needs that code, or just a bad implementation. среда, 31 октября 2018 г., 18:47:37 UTC+3 пользователь Jake Montgomery написал: > > It is highly likely that when go2 comes out, with

Re: [go-nuts] Heap of structs

https://tour.golang.org/ пятница, 2 ноября 2018 г., 1:10:25 UTC+3 пользователь Alex Dvoretskiy написал: > > I managed to implement it. It turned out to be easier... I was thinking > about using pointers to struct instead of variables.. > > On Thursday, November 1, 2018 at 12:49:55 PM UTC-7, Nath

Re: [go-nuts] does struct pointer *a == *b make sense?

true: a := &T{Name:"test", Child: &T{Name: "blah", Child: nil}} b :=&T{Name:"test", Child: a.Child} and it's not "childs" пятница, 23 ноября 2018 г., 6:20:31 UTC+3 пользователь Jesse McNelis написал: > > On Fri, Nov 23, 2018 at 2:06 PM Youqi yu > wrote: > > > > type T { > > Name string

Re: [go-nuts] Re: is it possible to speed up type assertion?

+1000 The most valuable comment in this thread IMO. Thank you. четверг, 2 февраля 2017 г., 13:41:25 UTC+3 пользователь Axel Wagner написал: > > I want to re-emphasize that all of these are micro-benchmarks. They say > nothing useful at all, as proven by this thread; in some circumstances, the >

Re: [go-nuts] GORM, saving values

In addition to exported fields, you don't need to import _ "github.com/lib/pq" just these "github.com/jinzhu/gorm" _ "github.com/jinzhu/gorm/dialects/postgres" четверг, 29 ноября 2018 г., 21:04:06 UTC+3 пользователь Mohamed Yousif написал: > > Beside exporting issue, you need to

[go-nuts] Re: invalid recursive type alias

Explained in proposal : Type > cycles > > In a type alias declaration, in contrast to a type declaration, T2 must > never refer, direc

[go-nuts] Re: pass interface

Of course. When you "pass a value whose type implements the interface" as an interface argument to a function, you in fact pass an *interface*. воскресенье, 9 декабря 2018 г., 23:23:41 UTC+3 пользователь Mark Volkmann написал: > > Is it possible to pass an interface to a function in Go? I don’t

Re: [go-nuts] Re: pass interface

interface {} понедельник, 10 декабря 2018 г., 5:05:12 UTC+3 пользователь Robert Engels написал: > > I mean reflect.Type not a type that is an interface. > > On Dec 9, 2018, at 6:53 PM, Space A. > > wrote: > > Of course. When you "pass a value whose type implem

Re: [go-nuts] what is the use of context in golang RESTful apis?

I just leave it here Context should go away for Go 2 воскресенье, 13 января 2019 г., 22:21:50 UTC+3 пользователь Tamás Gulácsi написал: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > There should be a "global" or parent

Re: [go-nuts] what is the use of context in golang RESTful apis?

Problems are fine. And developer should be able to take care of them. That's what he does. Context is basically a crutch. So are you proposing to make a crutch a language construct? четверг, 17 января 2019 г., 0:43:58 UTC+3 пользователь robert engels написал: > > I agree with all of those asse

Re: [go-nuts] what is the use of context in golang RESTful apis?

Go's package-level variables are also not "globals". And you can control access with exported/unexported names or exported/unexported package-level functions. PS: In Java everything is "class". четверг, 17 января 2019 г., 23:31:34 UTC+3 пользователь robert engels написал: > > Java does not ha

Re: [go-nuts] Dependency hell with Go modules

go list ./... пятница, 18 января 2019 г., 1:26:02 UTC+3 пользователь Francis Chuang написал: > > Thanks, Justin and Harmen. > > I deleted my go.mod and go.sum, then ran "go mod init ..." and "go test". > The list of dependencies in go.mod and go.sum is now a lot slimmer. I tend > to run my test

[go-nuts] Re: multiple binaries from a single directory with go modules?

Yes/ Don't use make and makefiles. > Is there some clever way of structuring a project like this with go > modules that I haven't figured out yet? > > Thanks, > > Tycho > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from

[go-nuts] Re: using docker for compiling

You simply need docker run <...> which will invoke smth like go build at the end. PS: The above Makefile is garbage. пятница, 1 февраля 2019 г., 21:59:53 UTC+3 пользователь Bojan Delić написал: > > I have Makefile that supports build in docker image, part of it looks > something like this: >

[go-nuts] Re: Handling connection retries on a highly-available service

It has absolutely nothing to do with mutexes/contexts/atomics or even Go (even if you program in Go). This is engineering or architecture task not the language thing, so you need to think like an architect. A lot of solutions possible if you add some sort of integration layer between P and Logg

Re: [go-nuts] Go - logo commercial use

That means that must give credit to author (Renee French) AND you must give credit to license itself All CC licenses require users to attribute the creator of licensed material, unless the creator has waived that requirement

[go-nuts] Re: Visual Studio Code oddity with Go

Nothing comes for free. For example, now you are wasting your (and others) time. среда, 20 февраля 2019 г., 17:14:21 UTC+3 пользователь Rich написал: > > I tried googling this but I not been able to find a solution, hopefully I > can ask this here and someone else knows how to fix this. I use

Re: [go-nuts] Re: Visual Studio Code oddity with Go

ang-nuts a welcoming venue to discuss > Go. > > The OP has tried to find out a solution and has been unable to. Asking > here seems like a reasonable place. > > On Thu, 2019-02-21 at 17:28 -0800, Space A. wrote: > > Nothing comes for free. For example, now you are wa

Re: [go-nuts] distribution of go executables

Mentioned license doesn't cover binaries produced by compiler, "binary form" there means go tools themselves, and stdlib only when redistributed separately as a whole in binary form. When stdlib is used to compile regular binary, it's not "redistributed", and there are no restrictions or specia

Re: [go-nuts] distribution of go executables

You are wrong. среда, 27 февраля 2019 г., 5:22:12 UTC+3 пользователь Ian Denhardt написал: > > Quoting Space A. (2019-02-26 20:58:40) > > > and stdlib only when redistributed separately as a whole in binary > > form. When stdlib is used to compile regular binary, it'

Re: [go-nuts] distribution of go executables

the stdlib. This means that the Go > license pertains. > > On Tue, 2019-02-26 at 18:35 -0800, Space A. wrote: > > You are wrong. > > > > > > среда, 27 февраля 2019 г., 5:22:12 UTC+3 пользователь Ian Denhardt > > написал: > > > > > > &g

Re: [go-nuts] distribution of go executables

e, what so ever. C'mon guys. ср, 27 февр. 2019 г. в 07:24, Dan Kortschak : > In-line > > On Wed, 2019-02-27 at 06:31 +0300, Space A. wrote: > > Executable is not derivative work to stdlib or anything. > > I think you'll find this is not the case in mos

Re: [go-nuts] distribution of go executables

repo and it's not the LICENSE's covered case. You are not restricted in any way. ср, 27 февр. 2019 г. в 17:41, Jan Mercl <0xj...@gmail.com>: > On Wed, Feb 27, 2019 at 3:20 PM Space A. wrote: > > > This is 100% clear case and you can distribute your compiled binaries

Re: [go-nuts] distribution of go executables

. It's not possible. So, that means that being part of the language, according to copyright laws, runtime can't be covered by copyright and restricted by a license. ср, 27 февр. 2019 г. в 17:36, 'David Golden' via golang-nuts < golang-nuts@googlegroups.com>: > On Wed,

Re: [go-nuts] distribution of go executables

ial" or "personal" complex use cases, etc. ср, 27 февр. 2019 г. в 17:55, Jan Mercl <0xj...@gmail.com>: > On Wed, Feb 27, 2019 at 3:47 PM Space A. wrote: > > > Mentioned license doesn't cover binaries produced by compiler, "binary > form" there mean

Re: [go-nuts] distribution of go executables

; On Feb 27, 2019, at 8:19 AM, Space A. wrote: > > You have very poor understanding of the subject, messing everything up. > There is no "derivatives" in Go's license terms *at all*. There is only > redistribution in binary and source form and it covers only what's

Re: [go-nuts] distribution of go executables

rect thinking. And again, it is all subject to litigation. > Whether you are right or wrong is up to the courts to decide. > > On Feb 27, 2019, at 8:55 AM, Space A. wrote: > > Regarding runtime - it's interesting (and separate question maybe), and I > would argue that runtim

Re: [go-nuts] distribution of go executables

solved it. > > On Feb 27, 2019, at 12:45 PM, Space A. wrote: > > It's very clear case. It will never become a case in a court. Otherwise, > if it ever will, I mean, compiling own program and distributing a binary > which used stdlib e.g. without kissing someone's ass -

Re: [go-nuts] distribution of go executables

d, 2019-02-27 at 17:19 +0300, Space A. wrote: > > You have very poor understanding of the subject, messing everything > > up. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiv

Re: [go-nuts] distribution of go executables

ght legislation as part of their employment. > > I'm done here. > > On Wed, 2019-02-27 at 23:19 +0300, Space A. wrote: > > Sorry? You have poor understanding and mess things, so what's wrong? > > Being > > dilatant is not crime, it's okay unless you start conv

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

Hi Pat, I also have some (quite a lot) years of Java, and absolutely agree with everything you said. And +1 to Ian's opinion on how free software projects must be driven. On Friday, May 24, 2019 at 5:24:41 AM UTC+3, Pat Farrell wrote: > > On Thursday, May 23, 2019 at 9:18:25 AM UTC-4, lgo...@g

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

Debian users vote for someone to become Debian Developer and give him right to vote? If no, how can it be "representative"? пн, 27 мая 2019 г. в 08:35, 'Axel Wagner' via golang-nuts < golang-nuts@googlegroups.com>: > This is a bit of an aside, I agree with everything Ian said, but: > > On Thu, M

[go-nuts] Re: Licence details of github.com/golang/sync

Are you creating your own programming language and tools and going to release it under own license terms? If not, and you're using this lib only to program your projects, there are no restrictions. четверг, 29 октября 2020 г. в 16:52:17 UTC+3, Denis Cheremisov: > Hi! > At my job we found these

Re: [go-nuts] Stop triggering firewall on Windows? Preset build path?

Just was going to say that =) суббота, 7 ноября 2020 г. в 23:01:17 UTC+3, Egon: > If you use `127.0.0.1:0` as your listening address then the firewall won't > trigger as well. > > On Saturday, 7 November 2020 at 15:20:06 UTC+2 Aleistar Markóczy wrote: > >> I may not be "using go run as a develo

[go-nuts] Re: Any recommendation for structured logging library in Golang?

If you want to go for structured and layered logging in JSON, consider https://github.com/francoispqt/onelog четверг, 19 ноября 2020 г. в 12:14:21 UTC+3, Denis Cheremisov: > Zerolog does the trick, need a bit of setup though for what you want > > среда, 18 ноября 2020 г. в 07:21:48 UTC+3, Chri

Re: [go-nuts] What are debian:buster-slim advantages vs alpine ones?

Hi Constantine, In our project we'd chosen debian-slim images vs alpine few years ago due to a number of reasons, if I recall arguments were like: 1. presence of libc 2. bugs and performance issues of alpine 3. security issues of alpine 4. debian is more suitable for testing with huge amount of

[go-nuts] Re: Generics, please go away!

Unfortunately it was expected that creators of the language will not resist forever being under the pressure of masses most which do not even code in Go, or not use Go as the main language and just following patterns and shitty idioms they took elsewhere. Generics are bullshit crap in its essen

Re: [go-nuts] What are debian:buster-slim advantages vs alpine ones?

We don't have a CGO in our project. We want libc and we value it because it's a gold standard which makes things stable and predictive. After all, container must just work, so we focus on our services other that testing and troubleshooting some side technology. For issues you can take a look at

Re: [go-nuts] Re: Generics, please go away!

Your message is perfect example of why most of the ppl who have their own different opinion and who have never been listened to or given that ability will just shut up, and stay away. вторник, 22 декабря 2020 г. в 14:01:53 UTC+3, axel.wa...@googlemail.com: > On Tue, Dec 22, 2020 at 11:09 AM M

Re: [go-nuts] Re: Generics, please go away!

> I have, plenty of times in the past, said myself that people who want generics should just use Java or C++. I'm not proud of saying that. It was a mistake. What if you actually were right? Have you ever been looking at it through "Clear is better than clever" prism? What if in 10 years you

Re: [go-nuts] Re: Generics, please go away!

> Again, it bears repeating: "The Go designers where against generics" is historical fiction. "The Go team is succumbing to public pressure" is political fiction. Both are simply false. Anyone saying either of those either misunderstood something someone on the Go team said, or is repeating fro

Re: [go-nuts] Re: Generics, please go away!

I didn't take part in few of the last surveys. However I filled that very last one and haven't seen any generics-related questions. It was also stated somewhere that some of them randomized? So I answered a lot of weird questions for anything, but language features. Anyways if Go is not poll-dr

Re: [go-nuts] Re: Generics, please go away!

Prime driver of Java's success were enterprises with huge amount of investments (money) into ecosystem along with all JSRs developed by companies and groups with J2EE becoming de-facto a standard for building enterprise applications. And all this was happening way before any generics. среда, 23

Re: [go-nuts] Re: Generics, please go away!

> Personally, though, I must say that the generics discussion has been going on for 10 years (and even more, if we don't limit ourselves to Go) and I don't - personally - believe that there is much hidden cost or surprising benefit left to be discovered. There is nothing hidden and nothing ne

Re: [go-nuts] Re: Generics, please go away!

What a ridiculous bullshit. пятница, 25 декабря 2020 г. в 19:49:26 UTC+3, Henrik Johansson: > Ok maybe this thread has gone on too long. > Both Java and C++ has benefited greatly from generics and most of their > respective communities wouldn't want them gone. I am pretty sure that's > what wi

[go-nuts] Re: Generics, please go away!

Go doesn't have classes and is not an OOP language. Classes (like in Java) vs structs (like in Go) is about inheritance vs composition, not about attaching fields and methods. Inheritance implies type hierarchy, child and parent, virtual functions, abstract and final implementations and so on s

[go-nuts] Re: Generics, please go away!

call. > We'll be able to use things like trees as simply as we use maps or slices. > I don't think we'll see the language turn into the grossness that is Java > or C++ because of it. > > On Wednesday, December 30, 2020 at 4:27:15 AM UTC-8 Space A. wrote: &

Re: [go-nuts] Generics - please provide real life problems

"runtime type-casting" "type safety something" "boilerplate" "amount of code" "benefit something" "greatly simplified" (for whom?) This topic has clearly shown that most people pro-generic have no *real world* problems that they struggle to solve, yet most of them don't even understand what *re

Re: [go-nuts] Generics - please provide real life problems

ding all their points as "bullshit", and you should > probably review the community code of conduct. > > If you've got nothing constructive to contribute, why bother? > > > - Dave > > > > On Dec 30, 2020, at 3:53 PM, Space A. wrote: > > >

Re: [go-nuts] Generics - please provide real life problems

aggressively turning to my personality. Do you protect this aggressive behavior just because you pro-generics and silently hate everything I will say (and me personally)? Because if you do, it's quite stupid. But I hope it's not. чт, 31 дек. 2020 г. в 07:51, Tyler Compton : > Space

Re: [go-nuts] Generics - please provide real life problems

to follow generally and by everyone: > > "I think your arguments would gain quite a bit more traction on this > list if you presented them in a more respectful way." > > a good exercise would be to review your messages from a different point > of view. read them as if

Re: [go-nuts] Re: Generics, please go away!

dding. > These compositional techniques are what give Go its flavor, which is > profoundly different from the flavor of C++ or Java programs. > https://commandcenter.blogspot.com/2012/06/less-is-exponentially-more.html чт, 31 дек. 2020 г. в 23:27, Alex Besogonov : > On Wednesday, Decemb

Re: [go-nuts] Re: Generics, please go away!

Missed your second question. > > But on the topic of generics, this entire thread seems alarmist. >> Generics will open a huge door for libraries to be written that will make >> our lives easier. I'm thinking specifically about data processing and >> machine learning. A lot of devs use Python r

Re: [go-nuts] Re: Generics, please go away!

s (opponent meant he doesn't want making Go like C++/Java). пт, 1 янв. 2021 г. в 05:16, Axel Wagner : > On Fri, Jan 1, 2021 at 1:23 AM Space A. wrote: > >> > Sorry to disappoint you (actually, no, not sorry) but OOP has nothing >> to do with inheritance. It's

Re: [go-nuts] Generics - please provide real life problems

You will always find use cases for anything even for absolutely useless things. Because real life is full of paradoxes, and people are always irrational. And you may be adding features again and again and you still will have more to add. This way anything including programming language becomes a bl

Re: [go-nuts] Generics - please provide real life problems

of "repetitive" code, abandoning "clear is better than clever" principle, and for infinite micro optimizations for every single nanosecond. пт, 1 янв. 2021 г. в 16:20, Axel Wagner : > On Fri, Jan 1, 2021 at 2:14 PM Space A. wrote: > >> So magic here is being able

Re: [go-nuts] Re: Generics, please go away!

he can explain his position if it makes any sense. Maybe I'm wrong and don't understand something, that's possible. So I'm not arguing for the sake of arguing. пт, 1 янв. 2021 г. в 16:48, Axel Wagner : > On Fri, Jan 1, 2021 at 1:57 PM Space A. wrote: > >>

Re: [go-nuts] Re: Generics, please go away!

fication of languages. Maybe I even did that, lol. пт, 1 янв. 2021 г. в 17:30, Axel Wagner : > On Fri, Jan 1, 2021 at 3:04 PM Space A. wrote: > >> > I don't see a lot of room for interpretation here. >> >> Well, I do. I do believe if you truly think he meant "

Re: [go-nuts] Generics, please go away!

bly, C, Cobol (prior 2002), or > Fortran (prior 2003). > > For example, C has instances but no methods. > > On Jan 1, 2021, at 6:56 AM, Space A. wrote: > > > Javascript is an incredibly popular language with non-inheritance OOP. > Or, at least, no inheritance at the typ

Re: [go-nuts] Re: Generics, please go away!

le state, > and can receive messages, which seems like a pretty good definition of an > object :D Hence, object oriented programming is possible. > > I don't really have an opinion on this. I just want to know if my > interpretation of your opinion was close, or way off base hehe. >

Re: [go-nuts] Generics, please go away!

using composition > rather than inheritance. Much of the Java stdlib uses both. It can be > argued that most usages of anonymous inner classes are composition rather > than inheritance. > > On Jan 1, 2021, at 1:59 PM, Space A. wrote: > > > Wait, I think I get it. A

Re: [go-nuts] Generics, please go away!

in Go as > well. You can create frameworks without using inheritance. > > On Jan 1, 2021, at 2:51 PM, Space A. wrote: > > Composition is just a principle, which can be implemented on different > layers by different ways. I'd say in Java you will be forced not only to > fol

Re: [go-nuts] Generics, please go away!

framework has nothing to do with OOP. Even the term framework is > misleading - there are many large “libraries” in C that I would consider a > framework. > > On Jan 1, 2021, at 5:05 PM, Space A. wrote: > > You keep replying with random sentences no matter what I say, just >

[go-nuts] Re: How to get VSCode to use different Go env vars for different directories in the same repo?

Hi, the solution would be: 1. Protect WASM source files with build flags so that when you open a "backend" main sources, IDE won't complain about "syscall/js", like this: // +build js,wasm 2. Open `wasm` directory in second instance of VS Code for which you would set GOOS and GOARCH for a works

Re: [go-nuts] The Generics Proposal has been accepted!

Shit show. вторник, 16 февраля 2021 г. в 21:52:43 UTC+3, skinne...@gmail.com: > I have been so very much looking forward to Go 2.0 and generics. Getting > it in 1.18 is the icing on the cake. I seriously did not think you could do > it considering that everyone was pulling you in different dir

Re: [go-nuts] The Generics Proposal has been accepted!

e language and what it brought to > you, and worried of what might the future bring to us. That's > understandable. But it doesn't give you the right to insult the community > this way. > > > On Wed, 17 Feb 2021, 1:50 pm Space A., wrote: > >> Shit show.

Re: [go-nuts] No generic, part -2

There is no rationale. They decided, and they implemented. No one from Go team ever took the argument against it seriously because "community" demands, blabla. And because Russ Cox with friends written an academic paper so this is now a question of pure science. Write your own and they could li

Re: [go-nuts] No generic, part -2

;s a new toy and biggest change to the language in years, because it's a "smart" way of doing things (we are mature programmers, aren't we?), because "type safety" and "performance" and so on so forth. сб, 13 мар. 2021 г. в 15:45, Martin Schnabel : > (sor

Re: [go-nuts] No generic, part -2

manipulate > facts, and second - stop being that dogmatic and negative here, please, for > the sake of all of us. > > In advance, thanks for your time and consideration. > > Cheers. > > Le sam. 13 mars 2021 à 12:34, Space A. a écrit : > >> There is no rationale. They

Re: [go-nuts] No generic, part -2

from you, based on the same > available data. But it's simply going to happen. So please be mindful of > how you communicate. And ideally, don't try to re-open this discussion with > the same arguments that have already been heard. It took enough time and > energy from everyo

Re: [go-nuts] No generic, part -2

ng man hours, you know that it will land somewhere. And I repeat, there wasn't a (public) question or discussion or anything regarding should we drop this topic entirely. сб, 13 мар. 2021 г. в 18:32, Axel Wagner : > On Sat, Mar 13, 2021 at 4:19 PM Space A. wrote: > >> > The d

Re: [go-nuts] No generic, part -2

в 19:39, Axel Wagner : > On Sat, Mar 13, 2021 at 4:59 PM Space A. wrote: > >> You are a smart guy, one of the smartest I have ever talked to. But it >> looks like you somehow missed a very obvious thing. The people you >> mentioned (and most of the so-called Go team) AFAIK

Re: [go-nuts] No generic, part -2

Sorry, of course it's Robert, my mistake. пн, 15 мар. 2021 г. в 05:30, Ian Lance Taylor : > On Sat, Mar 13, 2021 at 9:25 AM Space A. wrote: > > > > And Russ didn't write academic paper regarding it (before accepting > proposal in less than a month after it was pub

Re: [go-nuts] No generic, part -2

people who can change the consensus? How was it measured? A few days after Russ locked it, so nobody can even say a word against it if they wanted. So it looks very much that company management learned from "try" proposal. пн, 15 мар. 2021 г. в 05:27, Ian Lance Taylor : > On Sat, Mar 13,

Re: [go-nuts] No generic, part -2

t; On Saturday, March 13, 2021 at 11:35:23 AM UTC-6 axel.wa...@googlemail.com > wrote: > >> On Sat, Mar 13, 2021 at 6:24 PM Space A. wrote: >> >>> There is a huge difference between generics and some regular questions >>> like `Etag` implementation, isn't it?

Re: [go-nuts] No generic, part -2

d? You know that it's pretty easy to cheat with that system right? вт, 16 мар. 2021 г. в 01:03, Ian Lance Taylor : > On Mon, Mar 15, 2021 at 5:08 AM Space A. wrote: > > > > > For example, the multiple proposals that flowed out of > > > https://go.googlesource.co

Re: [go-nuts] No generic, part -2

is thread to ask for a poll. And Ian has been pretty clear about the flaws of that idea and that it's not how the Go project is run. I didn't ask for the poll, I just stated that there was no poll, as simple as that. вт, 16 мар. 2021 г. в 15:05, Axel Wagner : > On Tue, Mar 1

Re: [go-nuts] No generic, part -2

core values, such as simplicity over cleverness. And despite being claimed Go team doesn't know a way of improving language, other than adding features. вт, 16 мар. 2021 г. в 16:25, Axel Wagner : > On Tue, Mar 16, 2021 at 1:24 PM Space A. wrote: > >> That's absolutely up

Re: [go-nuts] Re: No generic, part -2

: > On 16-03-2021, Space A. wrote: > > >> This seems very dismissive of the many members of the community which > > *did* invest the time and energy to discuss the design for the past > years. > > When the contracts design was announced in 2018 > ><https://blo

Re: [go-nuts] No generic, part -2

you could improve your community, not the other way round to please you, it > doesn't happen in this planet. Generics is only a small part in Go with > minimal impact compare to other programming languages with ton of pain to > relearn. > > You have probably heard V language

Re: [go-nuts] No generic, part -2

f implementing the proposal. " Yep, sure. ср, 17 мар. 2021 г. в 02:08, Ian Lance Taylor : > On Tue, Mar 16, 2021 at 4:00 AM Space A. wrote: > > > > > The design draft was put up for discussion for months before it became > > a formal proposal. It was not new. > >

Re: [go-nuts] No generic, part -2

Can you provide any proof that there was an open public discussion? ср, 17 мар. 2021 г. в 02:12, Ian Lance Taylor : > On Tue, Mar 16, 2021 at 6:51 AM Space A. wrote: > > > > > (To be clear, your original claim was that there *was* no discussion - > which is at least eas

Re: [go-nuts] Healthy tinygo Was: No generic, part -2

I don't think Java failed on micros, for instance look at JavaCard, a lot of SIM-cards are running applets based on it. SIM cards can be a dying technology on itself, but still, I think there was a huge success. Not sure about other "small places" because I never touched them in my work. With rega

Re: [go-nuts] No generic, part -2

, 17 мар. 2021 г. в 14:57, Wojciech S. Czarnecki : > Dnia 2021-03-17, o godz. 14:27:51 > "Space A." napisał(a): > > > Can you provide any proof that there was an open public discussion? > > Can't you search for yourself? When I submitted my rough counterpr

Re: [go-nuts] Healthy tinygo Was: No generic, part -2

ects like tinyGo and in many others generics will add a significant cost to development. It's feasible, because it's not a rocket science, but not free. ср, 17 мар. 2021 г. в 16:29, Kevin Chadwick : > On 3/17/21 12:11 PM, Space A. wrote: > > I don't think Java failed on mi

Re: [go-nuts] No generic, part -2

discussion on dropping generics from your daily agenda and focusing and spending time on more important things, such as first class Android support. ср, 17 мар. 2021 г. в 22:44, Ian Lance Taylor : > On Wed, Mar 17, 2021 at 4:28 AM Space A. wrote: > > > > Can you provide any proof t

Re: [go-nuts] Re: now that the election is over can we please remove the political ad for golang.org

Btw, when this started (see original thread) I compared some main pages of websites of popular languages. And you know what? I didn't find stupid banner on Java or Rust websites, and on many others. Maybe they were smart enough to show it only to US visitors, idk. Anyways, Russ Cox obviously th

Re: [go-nuts] No generic, part -2

terpreting statements by members of the Go team in ways incompatible with > the actual words being said and b) speculating about the management process > at Google - without any evidence to base this speculation on. > > On Thu, Mar 18, 2021 at 1:11 PM Space A. wrote: > >> >

Re: [go-nuts] No generic, part -2

it is possible to have a productive conversation as long as > you behave this way. > > On Thu, Mar 18, 2021 at 1:48 PM Space A. wrote: > >> That's exactly what I'm saying, topic of dropping generics was never >> raised, so landing of some version of generics was impli

  1   2   >