Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Anonymous struct, difference between struct{}{} and {}

I have string to struct map in golang defined in the following way:

var Foo = map[string]struct{}{
    "foo": struct{}{},
}

Gogland by default marks this declaration as warning, saying "Redundant type declaration".

var Foo = map[string]struct{}{
    "foo": {},
}

Above code solves the warning, but I couldn't find any information about the difference between struct{}{} and {} declaration. Is it kind of a "short notation"?

https://play.golang.org/p/0Akx98XtB4

like image 764
hywak Avatar asked Oct 12 '17 10:10

hywak


People also ask

What is an anonymous struct?

An anonymous struct declaration is a declaration that declares neither a tag for the struct, nor an object or typedef name. Anonymous structs are not allowed in C++.

What is difference between struct and typedef struct?

In C++, there is no difference between 'struct' and 'typedef struct' because, in C++, all struct/union/enum/class declarations act like they are implicitly typedef'ed, as long as the name is not hidden by another declaration with the same name.

What is the difference between union and anonymous union?

An anonymous union is a union without a name. It cannot be followed by a declarator. An anonymous union is not a type; it defines an unnamed object. The member names of an anonymous union must be distinct from other names within the scope in which the union is declared.

What does it mean to typedef a struct?

The C language contains the typedef keyword to allow users to provide alternative names for the primitive (e.g.,​ int) and user-defined​ (e.g struct) data types. Remember, this keyword adds a new name for some existing data type but does not create a new type.


1 Answers

This:

struct{}{}

is a composite literal which contains the type (struct{}) and the literal's value ({}).

This:

{}

is also a composite literal without the type, just the value.

Generally you have to specify / include the type in the composite literal to let the compiler know what kind of (what "type" of) composite literal you're creating, hence the syntax is:

CompositeLit = LiteralType LiteralValue .

But when you specify a map composite literal, the types of the key and value are known from the map type, and thus may be omitted if you intend to specify values of those types. This is mentioned in Spec: Composite literals:

Within a composite literal of array, slice, or map type T, elements or map keys that are themselves composite literals may elide the respective literal type if it is identical to the element or key type of T. Similarly, elements or keys that are addresses of composite literals may elide the &T when the element or key type is *T.

(Note: due to an oversight, this is only valid from Go 1.5.)

like image 65
icza Avatar answered Nov 15 '22 08:11

icza