Re: [go-nuts] Re: What does a deadlock mean in golang?

2019-01-29 Thread Wim Lewis
On 29. jan. 2019, at 2:00 f.h., 伊藤和也 wrote: > In general computing, a deadlock is a situation where two different programs > or processes depend on one another for completion, either because both are > using the same resources or because of erroneous cues or other > problems.https://www.techo

Re: [go-nuts] go for robotic control, walking balance, quad flight control

2019-01-02 Thread Wim Lewis
On 29. des. 2018, at 9:05 e.h., Pat Farrell wrote: > I need a project to motivate myself into writing some non-trivial go. So I > want to learn about implementing control theory, sensors, etc. ... > So now I have 3 main questions: > 1) is go a bad choice for implementing this? > 3) what OS? (

Re: [go-nuts] Busted auth providers

2018-05-09 Thread Wim Lewis
On 8. maí 2018, at 8:53 f.h., jwint...@pivotal.io wrote: > It seems like `https://www.gitlab.com` needs to be added to the list of > busted auth providers in golang/oauth2. At the very least, has this been entered into gitlab's bug tracker? The best outcome would obviously be for gitlab to be f

Re: [go-nuts] Is Go a server side language or a client side?

2017-03-22 Thread Wim Lewis
On Mar 22, 2017, at 11:10 AM, Marlon Fez wrote: > I just heard about go, a new good language, but I cannot find the answer to > my question. Is this new programming language a server side (Back-End) > language or a client side (Front-End) language? > I currently work with C# for server side wor

Re: [go-nuts] Re: How do I convert a byte into BigEndian or LittleEndian?

2017-02-27 Thread Wim Lewis
On Feb 27, 2017, at 1:54 PM, Glen Newton wrote: > Ack! Sorry. > > I was referring to bit endianness https://en.wikipedia.org/wiki/Bit_numbering I think the golang package only deals with byte-oriented interfaces. Most CPUs can't address units smaller than a byte anyway, so endianness isn't rea

Re: [go-nuts] History: Does the _ (Blank identifier) trace its history back to VI's or something earlier?

2017-02-21 Thread Wim Lewis
If I had to speculate, I'd guess that the use of "_" for an anonymous or blank identifier in pattern matching and destructuring traces back to Prolog. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop recei

Re: [go-nuts] Re: Is there a reason go doesn't use the small string optomization

2017-02-01 Thread Wim Lewis
This discussion reminds me of another technique I've seen, which is to use tagged pointers to store strings of max length 7 with no allocations at all. Apologies if this has already been discussed to death here. For background: tagged pointers take advantage of the fact that most architectures

Re: [go-nuts] about sorting array

2017-02-01 Thread Wim Lewis
On Feb 1, 2017, at 4:56 PM, Néstor Flórez wrote: > OK, thanks for the clarification on the size being immutable.(I am trying to > teach myself Go) > > Still I want to know what happens when this statement is executed > sort.Ints(scores[:]) > Sort creates a slice > The slice is sorted > Sort copi

Re: [go-nuts] Priority cases in select?

2017-01-25 Thread Wim Lewis
On Jan 25, 2017, at 8:00 AM, 'Axel Wagner' via golang-nuts wrote: > It's also a feature rabbit-hole. I'd predict, that next up, someone who > experiences starvation wants to add weighted scheduling ("give this case an > 80% chance of succeeding and this other case 20%, so that eventually eith

Re: [go-nuts] Is there an easy way to check if two named types are identical across packages?

2016-06-14 Thread Wim Lewis
On Jun 14, 2016, at 2:43 PM, Aurélien Bombo wrote: > It's my understanding that the type checker considers named types identical > only if they're represented by the same pointer. > Thus it makes sense for types.Identical and typeutil.Hasher.Hash to return > incoherent results for say, > type a