If you are going to use time.Now() and a ‘change loop’, you should probably lock the thread to the Go routine to avoid an scheduler thrashing.
> On Jan 14, 2019, at 2:34 PM, Tamás Király <[email protected]> wrote: > > I'm simulating the internal clock of an embedded microcontroller... And this > sentence (and you!) gave the idea to use time.Now(). > > Thanks! > Tamas > > 9. jan. 14., H 21:12 dátummal Matt Ho <[email protected] > <mailto:[email protected]>> ezt írta: > Can you describe what task it is that needs to be updated every microsecond? > It seems like there should be a better to resolve the underlying need. > > M > > > -- > 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 [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > -- > 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 [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
