[go-nuts] Re: Advancing the container/set design?

2024-08-22 Thread Michael Whatcott
+1 On Monday, July 1, 2024 at 2:49:40 PM UTC-6 twp...@gmail.com wrote: > +1 on this. > > At the moment, every module that needs a set implementation ends up > creating its own, either using map[T]struct{} or map[T]bool. Having a set > implementation in the standard library would significantly i

[go-nuts] database/sql panic in 1.23

2024-08-22 Thread 'Nicolas Klaassen' via golang-nuts
Found this panic in database/sql introduced in Go 1.23.0 https://github.com/golang/go/issues/68949 I think it could use some attention. I mailed a 1-line fix in case it helps. We have been hitting it in tests and rolled back to 1.22 for now. -- You received this message because you are subscri

Re: [go-nuts] iterator method naming conventions

2024-08-22 Thread Ian Lance Taylor
On Thu, Aug 22, 2024 at 9:30 AM Adam Baratz wrote: > > I've been reading the iter pkg docs and I'm trying to understand a > distinction drawn there. > > It says that the iterator method on a collection type is conventionally named > All (and returns a Seq). However, the maps and slices packages

[go-nuts] iterator method naming conventions

2024-08-22 Thread Adam Baratz
Hi, I've been reading the iter pkg docs and I'm trying to understand a distinction drawn there. It says that the iterator method on a collection type is conventionally named All (and returns a Seq). However, the maps and slices packages handle this a little differently. They have All funcs tha

[go-nuts] Re: execution of a go program

2024-08-22 Thread 'Brian Candler' via golang-nuts
It's easy enough to demonstrate: https://go.dev/play/p/dvTJL5_UJrs You have a process with threads where goroutines run. When that process dies, all goroutines die too. They cannot live beyond, or independently from, the main process. On Thursday 22 August 2024 at 14:50:37 UTC+1 Adithyan Unni w

[go-nuts] execution of a go program

2024-08-22 Thread Adithyan Unni
i have a doubt i have a go routine in my code if my program ends still the go routine will work right . the doubt is that when my program ends is it the main function or the soure code as a whole ends the source code is converted to binary -- then we get a execution file then we do the code exe

Re: [go-nuts] Add yield types for range over function

2024-08-22 Thread 'Axel Wagner' via golang-nuts
I don't really understand the question. What I'm saying is 1. we don't want them to be defined types, because of the issue I described, so 2. it probably needs to be possible to have generic type aliases first and 3. once that is possible, we might add `Yield` and `Yield2` as type-aliases to the `i

回复: [go-nuts] Add yield types for range over function

2024-08-22 Thread 'lijh8' via golang-nuts
Hi, Do you mean that if the new Yield types are in the iter package,  it can be used after that? ``` type Yield[V any] func(V) bool type Yield2[K comparable, V any] func(K, V) bool type Seq[E any] func(Yield[E]) type Seq2[K comparable, V any] func(Yield2[K, V]) // not importing iter, so can

[go-nuts] How can SQL return both sql.Rows and sql.Result

2024-08-22 Thread Daniel Fava
Hi, How can I combine QueryContext and ExecContext so that both sql.Rows and sql.Result are returned? For example, if I have a stored procedure with: ``` insert into Users (Username) values ('JohnDoe'); select X = 1, Y = 'one'; select X = 2; update Transfers set Value = 10 where Value = 0; ```