Hi, I wrote a package to hash any comparable type:
https://pkg.go.dev/gitlab.eif.urjc.es/paurea/dohash
In contrast to https://github.com/dolthub/maphash it can use any
hash function (as long as it implements hash.Hash64) and it does
not depend on any internal detail of the runtime.
It works by i
; >
> > On 1/13/23 07:20, Gorka Guardiola wrote:
> > > According to the spec it seems like it is legal to shadow a type with a
> > > variable, even a builtin type.
> > > Is there any specific rationale for this? I guess that it makes scoping
> > > checks e
These programs compile and work according to my reading of the spec, but I
found them surprising.
https://go.dev/play/p/EUZ_28jge1N
https://go.dev/play/p/NMhR1Nq1COw
According to the spec it seems like it is legal to shadow a type with a
variable, even a builtin type.
Is there any specific ration
On Sat, Nov 12, 2022 at 12:40 AM Mike Schinkel wrote:
> Hi G.,
>
> It takes guts to make a proposal in the Go community. Kudos for doing so.
>
Or recklessness :-). Thanks.
>
> However, the issue with this proposal for me is the issue I have with
> almost(?) every other proposal to handle erro
On Wed, Nov 9, 2022, 20:47 Ian Lance Taylor wrote:
> On Wed, Nov 9, 2022 at 10:40 AM Gorka Guardiola wrote:
>
> Seems related to https://go.dev/issue/54361, although due to inject it
> is not the same.
>
I hadn't seen that proposal.
>
It is similar in the sense tha
I have the following idea [1] for decluttering error handling in go. It
looks similar to others already presented, but is is different in important
ways:
1) It does not interfere with or use panic
2) Is general enough that one can wrap errors with other errors or check
different kinds of errors.
3
Other languages seem to be ok.
The link has been down with a 404 error for quite some time.
Does anybody know why?
Thanks,
G.
--
- curiosity sKilled the cat
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and st
