proposal: avoid redefining the struct content in literal composite

[metal3d]

Hello,

I often need to create composed types to parse structured data. And I wonder if we could avoid redefining the content of the struct that we declare inside another.

For example:

https://goplay.tools/snippet/DLsNoPTpvh2

The struct is like this:

type Result struct {
    Name string `json:"name"`
    Data []struct {
        Title  string `json:"title"`
        Author string `json:"author"`
    } `json:"data"`
}

Parsing a JSON file with this is OK. But, if I want to create a document with this, I need to write:

r := &Result{
   Name: "Foo",
   Data: struct { // we already defined the struct content...
        Title  string `json:"title"`
        Author string `json:"author"`
   }{
         Title:  "test",
         Author: "me",
    },
}

It's a pity to not be able to write it like this:

r := &Result {
   Name: "Foo",
   Data: {
        Title:  "test",
        Author: "me",
    },
}

Of course, I understand that if "Data" is a slice of structs, it needs a better syntax.

That's just an idea.

[seankhliao]

Duplicate of #35304

[metal3d]

@seankhliao I'm sorry, but I don't see in what it's the same topic as #35304 - what I suggest here is not about anonymous struct, but about typed struct declared in another type that needs to be redeclared in assignation.

Is there anything I badly explained? (it's possible, English isn't my mother thong)

[seankhliao]

then #21496