Re: [go-nuts] Character Replacement/Algorithm for Replacement

Do you have an example? I'm assuming that the replacement is one character for another. (ie.: not one character being replaced by a group of characters). Regarding to finding the positions to replace you can't beat O(n) complexity as you must look at least once at every character on the source st

Re: [go-nuts] Alternate syntax for Go2 generics and contracts

I agree with Tristan in regards to orthogonality. Seeing the draft with all those complexities added to the language made me quite uneasy about this proposal. When I first started learning Go I was one of the first people to raise a hand and complain about the lack of generics in the language. Now

Re: [go-nuts] Re: [golang-dev] go doesn't need generics, but if they do...

+ 1,000,000 > > > Exactly, Go is very simple, and ideal for the cases I pointed out in the > original post (and I’ll add, micro-services too), and so far all of the > proposals that seem to be gaining traction don’t continue that design > paradigm. > > -- You received this message because you ar

Re: [go-nuts] Generics - Why contracts?

Having an external tool to write/validate contracts sounds more like a hack than a proper solution. It's kind of the same reason why I dislike generators. You have to learn an "alien" syntax that doesn't quite fit the rest of the language. If we are going that way, why not implement a full fledged

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

it pays to learn to code things in different ways, that why I'm not bothered by writing non-generic code in Go. I'm just exercising a different part of the brain. In the end, if the Go team makes a bad decision and Go stops being fun, it's just time to move on to a new thing. It's n

Re: [go-nuts] Re: how to implement channel priorities?

reads both channels and insert them into the min-heap. goroutine 2 reads from min heap and do the processing. Daniela Petruzalek Software Engineer github.com/danicat twitter.com/danicat83 Em qui, 14 de fev de 2019 às 15:34, escreveu: > select { > case highVal := <- high: > case lowV

Re: [go-nuts] Concerning the level required to contribute to Go

tools. I am yet to make a great contribution to the Go code base, with lots of Go code and rainbows, but I hope my experience can show you that you don't need to be a rocket scientist to contribute to it. Best, Daniela Petruzalek Software Engineer github.com/danicat twitter.com/danicat

Re: [go-nuts] The "leave "if err != nil" alone?" anti-proposal

cial cases aren't special enough to break the rules... we don't need a different type of error handling. Readability counts... explicit is better than implicit... I wish we had a Zen of Go and followed it. Daniela Petruzalek Software Engineer github.com/danicat twitter.com/danicat83

Re: [go-nuts] Разбить массив чисел на два массива

I'm not sure if that is a good idea 😅 https://play.golang.org/p/Mj77pgsaVsB Daniela Petruzalek Software Engineer github.com/danicat twitter.com/danicat83 Em dom., 1 de dez. de 2019 às 17:07, Marcin Romaszewicz escreveu: > It's very simple to do that: > https://play.golang.o

Re: [go-nuts] Re: Go mindshare is low & ~flat, per Google Trends

> https://groups.google.com/d/msgid/golang-nuts/8dc0b035-d5fe-4ccf-87d3-84c0978c881d%40googlegroups.com > <https://groups.google.com/d/msgid/golang-nuts/8dc0b035-d5fe-4ccf-87d3-84c0978c881d%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Daniela Petruzalek Software Engineer