Re: [go-nuts] Re: Validation checks in Go

https://play.golang.org/p/d_fQWzXnlAm If you are going to use panic, then choose a place where you can recover gracefully and report the error. I do agree, that it is an mistake to return an error code if your assignment was to write a function that only has valid input. The software engineer

[go-nuts] Re: I am confused.

If you want to learn GO, the easiest and best way to start is with https://play.golang.org/ You write your code using any browser, run the code on a remote server, you can see the results, you can share your code simply by sharing a link. There are all sorts of documentation online. If you

[go-nuts] Re: Go license and fitness for purpose

Regarding this statement. > THE AUTHORS OF THIS SOFTWARE DID NOT INTENTIONALLY MAKE MISTAKES OR > INCLUDE PRACTICAL JOKES If you place software out in the wild, and you have a LICENSE with no warranty and indemnification and terms of service and imprint - You are not protected from

[go-nuts] Re: Validation checks in Go

I agree with Matt, using panic is fine when you are debugging. I do not usually do panic in production code unless it is because of the loss of some asset required to start. GO has robust error handling. You should write the function to return an error. If you deploy your program to a client

Re: [go-nuts] Re: I am confused.

https://invite.slack.golangbridge.org/ You Must be Over the Age of 16 to use chat server. You must be over age 13 to use GitHub On Sat, May 26, 2018 at 11:07 PM wrote: > Have you not seen my post about joining a chat server? > Instead of waiting a day or so for each

Re: [go-nuts] Re: How to refactor out this function

o say when you finally meet Send. > > io.RuneReader will ReadRune, not ask a Rune to Read. :) > > On Wednesday, August 8, 2018 at 6:27:58 AM UTC-7, David Skinner wrote: >> >> I cannot speak for the community, only for myself. >> >> I like to

[go-nuts] Re: How to refactor out this function

I cannot speak for the community, only for myself. I like to use NounVerb combinations that make sense with the package name. package.NounVerb() handles.HelloSend() I can then define the interface as VerbEr type HelloSender interface { HelloSend() } My son spent too

[go-nuts] Re: Local cache of dependencies

Modules rarely disappear but when they do it can have a profound impact on a project. I am really paranoid so I sometimes fork a project to a private repo just to have it on hand just in case. I have used git submodules from the git command line as a solution. I still do, but I would not

[go-nuts] Re: Generis, yet another Generic go code generator... ;)

I am very, very, old school, grew up with ASM and Macro Assembly. I really appreciate this. I prefer to write Go code in a purely idiomatic way but there are times i just want to finish the job and ship it. Thank you for sharing. On Sunday, March 24, 2019 at 4:23:52 PM UTC-5, Ecstatic Coder

[go-nuts] Re: Go vs C speed - What am I doing wrong?

For me, my C code is very micro-efficient so it generally runs faster than Go, but it takes me up to 4 to 5 times longer to write things in C than it does to write things in Go. If the resulting Go code is not fast enough, I have three solutions: 1. Run the profiler to find the bottleneck,

[go-nuts] Re: 紧急！！中国一线互联网公司招聘云容器GO研发技术Lead

Thank you for the invite. I would be pleased to be of assistance. While I do not wish to relocate to Chine, I would very much like to visit. I am located in Arkansas USA and have some limited experience with Mandarin. On Wednesday, April 17, 2019 at 7:34:22 AM UTC-5, chandler song wrote: > > >

[go-nuts] Re: Go if else syntax .. suggested replacement

I consider this to be a non-issue. There are two ways of writing in a new language. - You can learn the language as defined. - You can write it the way you like it and convert to what is required and then convert every one else's stuff to what you like. Go makes it fairly easy for

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

I only rarely use generics in Go. When I do so, it is implemented using the +generate. The repos with my generics stuff is not public. If they were, they might be incomprehensible. While I rather like Fo, the thought of C++ style generics makes me cringe. Code must compile but it needs to be

[go-nuts] Re: A good indicator of code quality

Back in 1988, I was tasked with a code review for what seems like 150 programmers. Now I am very lazy, being a good programmer, I am willing to spend all day automating a one hour job. They were all using an in house OOPS language. I performed a cluster analysis of metrics using a Comal

[go-nuts] Re: About the Google logo on the new Go website

It is my opinion that it is only polite to acknowledge corporate sponsors in a tangible way. The problem is if you have only one corporate sponsor. I know for a fact that members of the Smythe Group have contributed time to Go dev without compensation. Many other people have also made

[go-nuts] Re: Fuchsia Programming Language Policy

I quite understand their critic. - GC sometimes causes me problems that result in me writing part of my code in C++ or ASM. But over the last 10 years the GC seems to be mostly improving and that is rarely a problem for me. - I used to write engineering, accounting, and legal apps

[go-nuts] Re: CSS-like selectors for Go AST?

We have something like that on the drawing board, but right now it is very much vaporware. The basic concept that we are using, is that you create a new instance of a type of input and specify a CSS style of class. The actual implementation of the class may vary depending upon whether the DI

[go-nuts] Re: Reduced error handling noice

This looks like something I might have done. However, my preference would be to write a wrapper MustGetParameter receives string field, calls store.GetParameter(field), returns parameter or panics. You may then use defer func() { globalErr = recover()} tenantID, err1 :=

[go-nuts] Re: Better formatting of struct literals

I very much like things that improve readability. On Monday, October 26, 2020 at 11:27:23 AM UTC-5 Eric Lindsey wrote: > Recently, I gofmt'ed a block of code in a file and this is what I ended up > with: > > embed := { > Color: MembershipEmbedColor, > Description: "This collection is

Re: [go-nuts] Go 2 review process

While I have over 50 years of programming experience, I am also quite old and sometimes have senile moments. I once wrote an extremely well-written bug report complaining about the use of the backtick which is not on my keyboard, explained why it should not be used, and then presented a

Re: [go-nuts] [proposal] Make go compiler work with different syntax versions in same project to support adaptivity

A handyman can do many things. But domain-specific experts like plumbers, electricians, and carpenters are far more skilled and efficient. Statistical analysis of psycholinguistics indicates that there exist specific modes of thinking, no one syntax will ever be the best syntax for all modes

Re: [go-nuts] Re: Why we don't have simple throws error statement

I do not consider error handling an issue but then again I tend to either use the Doit() err{} or MustDoit(){} panic and then use DI (dependency injection implemented by interface) for error-handling so that I can get an email when we get a new error. So then it would be

[go-nuts] Re: [generics] I think it's better have higher perfomance than lower compiling time

I remember going on a two-hour lunch break at a Cajun restaurant and returning to my office to discover that my precompiled C++ headers were still compiling. I really love that Go compiles quickly and links quickly. The day comes when code needs to ship, final compile, and final quality

Re: [go-nuts] Re: [generics] I think it's better have higher perfomance than lower compiling time

optimization level, meaning that these > bugs can be missed during development. Go's memory safety would probably > make this significantly less of a problem, but it still concerns me > somewhat. > > On Fri, Jun 19, 2020 at 6:46 PM David Skinner > wrote: > >> I remember

[go-nuts] Re: The next layer of abstraction for Go development?

I am very very old, and very old school, so I always start with UMLs and ERDs and design my apps long before I do any coding. These flowcharts are visual representations that are concise and easy to understand and they are saved as XML which can be parsed by a Go program controlled by +generate

Re: [go-nuts] Go 2 review process

Not having a GitHub account is a non-issue. - It is an issue now because the enhancement process is on GitHub issues which does not include voting or weighting of votes. It is a trivial matter to use gohugo.io with a package that integrates GitHub issues as the repository for comments. ---

Re: [go-nuts] Go 2 review process

I really like Markus Heukelon's suggestion. There is no need for the Go team to evaluate each proposal, that is a silly waste of a valuable and limited resource. Having a list of all proposals with voting means that the most popular items float to the top and the worst float to the bottom and

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

I considered generics so important to our workflow that I added it quite some time ago, Go is an implementation language, you may implement anything you like with it. If you do not like the way it does something, you can use it to create a different language, that is what real programmers do.

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

CAHC_roGwVqqk9aiNv0h7Pa6XDDBWrr3HRBBMk9bHaZqjcrUG%3DQ%40mail.gmail.com?utm_medium=email_source=footer> > . > -- Respectfully submitted, David Lynn Skinner Secretary, Davsk Ltd Co <http://stackoverflow.com/users/3886366/david-skinner> <http://github.com/ComalDave/> <htt

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

98d-1c4e183189dbn%40googlegroups.com?utm_medium=email_source=footer> >>>> . >>>> >>> -- > 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://gr

[go-nuts] Re: nice user survey re Go-lang

Thank you for sharing. I think the most important things to learn from this survey are the problems identified. For example, This is an important opportunity for new users if they have not used the debug tools to take careful notes and create precise documentation for others. On Wednesday,

[go-nuts] Re: More info on gopls woes

We had a similar issue last year due to some problem with a corporate proxy. You might refer to https://github.com/golang/vscode-go/issues And test to see if your problem is related to your proxies. On Monday, March 1, 2021 at 5:21:52 PM UTC-6 oldCoderException wrote: > Hi everyone, > > I've

Re: [go-nuts] Contrary to popular opinion...

I have a wonderful video of a GO program I wrote over 5 years ago which will not compile today due to my failure to vendor one lost module. I too had multiple paths in my GOPATH and it varied upon the client. I consider the new modules an improvement but the adaptation has not been without

Re: [go-nuts] Need help/tips on golang compiler souce code reading

Ian, I very much appreciate your taking the time to provide the history here. I am almost inclined to suggest that the OP create a design document much the way an engineer creates an as-built design before creating a new design. For my part, I would be willing to assist the OP on an occasional

Re: [go-nuts] Error handling

I wanted to express my thanks to Mickael McKinnus for his research. I am someone who is quite happy with the error handling in Go as it lets me implement whatever I like, I must say it is obviously flawed from the standpoint that the proper constructs are not part of the language but part of

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

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 directions. Well Done! Defining the job is 90% of the project. The coding and testing