Re: [go-nuts] Re: couldn't print numbers ordered with goroutine
On Sun, 2024-04-21 at 15:06 +1200, Justin Israel wrote: > And really I wasn't even commenting on the nature of the channel. > Only the scheduling of the goroutines. Buffered or not, they would > still be random order right? Absolutely. Your answer was spot on. The issue is the ordering of the goroutines' execution, not the behaviour of channels. I just wanted to clarify the comment that responsed to that. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/7d71acf0bcf19fbf2ddb5264485f328e08f323fa.camel%40kortschak.io.
Re: [go-nuts] Re: couldn't print numbers ordered with goroutine
On Sun, Apr 21, 2024, 2:07 PM 'Dan Kortschak' via golang-nuts < golang-nuts@googlegroups.com> wrote: > On Sat, 2024-04-20 at 18:55 -0700, Robert Solomon wrote: > > channels are not queues, as Justin said > > They can be; buffered channels are queues. > > From https://go.dev/ref/spec#Channel_types > > > Channels act as first-in-first-out queues. For example, if one > > goroutine sends values on a channel and a second goroutine receives > > them, the values are received in the order sent. And really I wasn't even commenting on the nature of the channel. Only the scheduling of the goroutines. Buffered or not, they would still be random order right? > > -- > 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://groups.google.com/d/topic/golang-nuts/oMFIFDi_Irg/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/05501e4c795fdcb4b91ffa3c35f95984772c9cde.camel%40kortschak.io > . > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAPGFgA2xbShBJNd1Sg2BOOsN%2BtU0050PcbDiGtOCNULsQG%3Dwig%40mail.gmail.com.
Re: [go-nuts] Re: couldn't print numbers ordered with goroutine
On Sat, 2024-04-20 at 18:55 -0700, Robert Solomon wrote: > channels are not queues, as Justin said They can be; buffered channels are queues. >From https://go.dev/ref/spec#Channel_types > Channels act as first-in-first-out queues. For example, if one > goroutine sends values on a channel and a second goroutine receives > them, the values are received in the order sent. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/05501e4c795fdcb4b91ffa3c35f95984772c9cde.camel%40kortschak.io.
[go-nuts] Re: couldn't print numbers ordered with goroutine
channels are not queues, as Justin said
On Saturday, April 20, 2024 at 8:18:18 PM UTC-4 Justin Israel wrote:
> On Sunday, April 21, 2024 at 11:18:24 AM UTC+12 Taňryberdi Şyhmyradow
> wrote:
>
> Hello guys,
> For the following lines, I wanted to print numbers in ordered, but
> couldn't. Could you please help me and explain the reason
> Thanks in advance
>
> ```
> numbers := []int{1, 2, 3, 4, 5}
>
> // Create a buffered channel to handle multiple values
> printed := make(chan int, len(numbers))
>
> for _, n := range numbers {
> fmt.Println("Sending", n, "to the channel")
> go func() {
> printed <- n
> }() // Pass the value of n by copying it
> }
>
> // Receive all values from the channel in a loop
> for i := 0; i < len(numbers); i++ {
> fmt.Println(<-printed)
> }
> ```
>
>
> When you start a bunch of goroutines in a loop, there is no guarantee as
> to what order the scheduler will start each one.
> Thus you will see them delivered in different orders on each run. You have
> to decide on some form of synchronization. Maybe you choose to run a single
> goroutine worker that will loop over the source slice, and push the values
> into the channel in order. Or maybe you will keep using many goroutines but
> collect them all in the receiver, sort them after the last value is
> received, and then print them out. Or, maybe your receiver will have some
> kind of buffering where it collects values and only prints them when it has
> the next one in sequence.
>
>
>
> --
> Tanryberdi Shyhmyradov
>
>
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/2b4dcdb7-28fc-46e1-90c2-7c01aeac1e44n%40googlegroups.com.
[go-nuts] Re: couldn't print numbers ordered with goroutine
On Sunday, April 21, 2024 at 11:18:24 AM UTC+12 Taňryberdi Şyhmyradow wrote:
Hello guys,
For the following lines, I wanted to print numbers in ordered, but
couldn't. Could you please help me and explain the reason
Thanks in advance
```
numbers := []int{1, 2, 3, 4, 5}
// Create a buffered channel to handle multiple values
printed := make(chan int, len(numbers))
for _, n := range numbers {
fmt.Println("Sending", n, "to the channel")
go func() {
printed <- n
}() // Pass the value of n by copying it
}
// Receive all values from the channel in a loop
for i := 0; i < len(numbers); i++ {
fmt.Println(<-printed)
}
```
When you start a bunch of goroutines in a loop, there is no guarantee as to
what order the scheduler will start each one.
Thus you will see them delivered in different orders on each run. You have
to decide on some form of synchronization. Maybe you choose to run a single
goroutine worker that will loop over the source slice, and push the values
into the channel in order. Or maybe you will keep using many goroutines but
collect them all in the receiver, sort them after the last value is
received, and then print them out. Or, maybe your receiver will have some
kind of buffering where it collects values and only prints them when it has
the next one in sequence.
--
Tanryberdi Shyhmyradov
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/ae085bdf-544f-4958-b85f-e36dcaea8ca7n%40googlegroups.com.
