Re: [go-nuts] Linting

I have no complaints, let me be clear about that. Just advice, for all I've learned in my cariere is that maintenance is happening more than the first version of something creative. But I've still got hope that one day I might understand some complex coding that I didn't write myself. I'm happy to

Re: [go-nuts] Linting

On Tue, Dec 13, 2022 at 2:31 AM Brian Candler wrote: > > With that in mind, I'd respectfully suggest that your starting point should > be to pick one of these "over complex" functions, understand it fully, and > rewrite it in what you consider to be a simpler/clearer way which does not > break

Re: [go-nuts] Generics in gollvm

On Tue, Dec 13, 2022 at 9:09 AM Andrey Bokhanko wrote: > > Do you have any idea on when generics support in gofrontend might be finished? Sorry, I don't. I understand the interest but I simply don't know. Ian -- You received this message because you are subscribed to the Google Groups "golan

Re: [go-nuts] Generics in gollvm

Hi Ian, Thanks for the update! Do you have any idea on when generics support in gofrontend might be finished? (To clarify, I don't want to "push" you at all; understandably, you have a lot on your plate and have to juggle different priorities. My only point is to have at least some understand

Re: [go-nuts] Linting

I totally understand that you put the ball back to me. My message is not to blame anybody and I think I didn't do that. People might be offended, but I'm just the messenger. The trick is, if we want software to survive, we should always check if it is understandable and maintainable and that is my

Re: [go-nuts] Linting

I'd say that in an entire programming language and runtime environment like Go, there is much which is inherently complex. Just think about things like garbage collection and asynchronous preemption. A linter which creates dumb metrics like "number of lin