Re: [go-nuts] Map with a struct, can someone tell me what changes should I do. It is a silly error

Thank you! On Sat, Oct 30, 2021 at 2:36 AM Kurtis Rader wrote: > You didn't tell us what the problem is or the version of Go you're using. > In any event, your code has a couple of problems. This line > > classA.Multiplestudents[s1]={Name:"s1",RollNo:10, AddressList: > Address{Doorno:10}} > > sh

Re: [go-nuts] Is there a place to track the proposal about "reflection on type arguments"?

Thanks for your reply. Actually I am planning to build a mock framework which only receive a type parameter then mocks methods of such type. So that I need to get the type information of the type parameter. Currently I found I can do it by this way: ``` func (m *mock[T]) PrintType() { x := r

[go-nuts] Re: Help getting database/sql pooling merged

Just a quick bump to see if we can get this over the line in time for the 1.18 release freeze in just a couple of days time? On Sat, 23 Oct 2021 at 00:29, Steven Hartland wrote: > There's been a long standing bug > in database/sql pooling which > means

Re: [go-nuts] Map with a struct, can someone tell me what changes should I do. It is a silly error

You didn't tell us what the problem is or the version of Go you're using. In any event, your code has a couple of problems. This line classA.Multiplestudents[s1]={Name:"s1",RollNo:10, AddressList: Address{Doorno:10}} should be classA.Multiplestudents[s1]= &studentdetails{Name:"s1",RollNo:10, Add

Re: [go-nuts] Is there a place to track the proposal about "reflection on type arguments"?

On Fri, Oct 29, 2021 at 10:04 AM Jindong Zhang wrote: > > I see there is a discussion about "reflection on type arguments" at the end > of type parameters proposal (generics). > I am interested in this but don't find any futher discussion about this topic. > So is there a place I can get the pro

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

In order to standardize something, you need to establish things thanks to which you are able to express what you want to say. For example a Notation. The Go Reference manual uses Extended Backus-Naur Form (EBNF) for that and this part is just expressing that. Think of this point not as "Go docume

[go-nuts] Map with a struct, can someone tell me what changes should I do. It is a silly error

package main import ( "fmt" ) type Address struct { Doorno int64 } type studentdetails struct { Name string RollNo int AddressListAddress } type class struct { //ueCtx gnodeb_proxy_util.RanUeContext

[go-nuts] Is there a place to track the proposal about "reflection on type arguments"?

Hi there, I see there is a discussion about "reflection on type arguments" at the end of type parameters proposal (generics) . I am interested in this but don't find any futher discussion about this topi

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

Thank you Patryk Węgrzynek for these notes. I often feel uneasy when things like "ways of comunications” are unclean to me just at the beginning of reading of text. I like have everything clear at start and you help me clear some mess in my head. Best Kamil pt., 29 paź 2021 o 16:00 Kamil Ziemian

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

Thank you Jan Marcel, now I understand this part of Spec. I now will go back to read rest of it. Best Kamil piątek, 29 października 2021 o 13:29:16 UTC+2 Jan Mercl napisał(a): > On Fri, Oct 29, 2021 at 12:53 PM Kamil Ziemian wrote: > > > > From what I understand about EBNF production_name shou

golang-nuts@googlegroups.com

Based on this recommendation, I started Bill's class and got the book. I like the class a lot. Thanks for the post On Sat, Oct 23, 2021, 7:23 PM wrote: > golang-nuts@googlegroups.com > > Google > G

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

On Fri, Oct 29, 2021 at 12:53 PM Kamil Ziemian wrote: > > From what I understand about EBNF production_name should be defined using > EBNF notation in manner like below. > > production_name = something1 | something2 > > But I don't see such definition in Spec. Because production_name is a termin

[go-nuts] Re: Amateur's questions about "Go lang spec"

>From what I understand about EBNF production_name should be defined using EBNF notation in manner like below. production_name = something1 | something2 But I don't see such definition in Spec. Best Kamil czwartek, 28 października 2021 o 21:31:07 UTC+2 seank...@gmail.com napisał(a): > There