Caleb Spare

@mknyszek I find it hard from reading the proposed signatures and doc comments to understand what `S` and `cleanupValue` *are*. Could you clarify that a bit? It might also help...

How does this interact with the unique package (#62483)? Isn't it possible for a user to implement unique (or at least solve the same problems that unique solves) using weak...

To quote #61515: > * `b.Loop` could be a clear signal to the compiler not to perform certain optimizations in the loop body that often quietly invalidate benchmark results. To...

Thanks for filing this issue. I also ran into this recently when trying to use `sql.Null[T]` more widely. One way to look at the issue is that there is an...

@jba I agree it looks like a bug fix, and without thinking too hard about it it seems like the right fix. I'm just commenting that you can construct some...

@sGy1980de Here's an example: ``` type S string func (s *S) Scan(src any) error { switch src := src.(type) { case string, []byte: *s = S(src) default: return fmt.Errorf("unexpected type...

Who makes the call about whether this fix is acceptable? The database/sql owners are @bradfitz and @kardianos. Or should we make a proposal? Otherwise I'm happy to send a CL...

@timothy-king I don't think that matters here. Range-over-integer is fairly minor syntactic sugar. The issues that `b.Loop` addresses are *not* about saving the user a few characters of typing; they...

I have wanted int128 for representing currency in some situations.