First off, I am really loving Go overall. I probably did what many do and
started out with less Context use and now it is becoming a standard for a
few tiers which I see was in a blog somewhere from Google as well. What I
haven't been able to find is if there has ever been a conversation on
m
cleanup code
> written in Go today, by introducing race conditions, not to mention
> fundamentally change how error handling has to work.
>
> People have pointed out real problems with the current situation, but I
> haven't seen a good solution yet.
>
> -Ian
>
> Quot
I could be wrong but this seems like over-complicating what you need. Just
return the pointer to your foo struct. If you have your NewFoo return your
pointer it should be accessible but not modifiable and a quick test I just
did seems to validate that. Let me know if I misunderstand, in packa
I havemf eun tour code bit the lower case "eye" jumps out as something to look
at... "case iD".
Hope that helps. A debugger to walk through should help!
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop
Lol! Lack of sleep is real... apologies for the horrible keyboard offset
below. What I was trying to suggest was to check the case on your ID field.
In your struct it is all capitalized. The constant and my guess the
dereferenced string is a lower case i with a capital D. Running your code
I agree generally with constraint and interface really being different
should be named differently. Is the simplest solution that is also clean
to have a constraint type that only allows the type parameter (for now) and
can also include an interface type? The generic definitions can allow for
b3e-f811e61c01ben%40googlegroups.com.
Sincerely,
David Suarez
Gallup Strengths Finder: Achiever * Strategic * Relator * Ideation * Learner
https://www.linkedin.com/in/davidjsuarez/
--
You received this message because you are subscribed to the Google Groups
scr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/aa9b40d9-b154-48dd-bb52-62f139e3bceen%40googlegroups.com.
Sincerely,
David Suarez
Gallup Strengths Finder: Achiever * Strategic * Relator * Idea
The number of posts on this topic piqued my curiosity so I hope to add some
considerations after doing some research on this trail that I hope you find
useful.
TL;DR: It is possible that the reason for the interest in improving
"exception handling" in the proposed way is driven by individuals