New
does not initialize the memory, it only zeros it. It returns a pointer to a newly allocated zero value.
Make
creates slices, maps, and channels only, and it returns them initialized.
What does "initialized" mean in this context? What other differences are there between new and make?
The new function in Golang allocates memory but does not initialize it as the make function does. new returns a pointer to the newly allocated zeroed value of type T .
Golang make() is a built-in slice function used to create a slice. The make() function takes three arguments: type, length, and capacity, and returns the slice. To create dynamically sized arrays, use the make() function. The make() function allocates a zeroed array and returns a slice that refers to that array.
You need make() to create channels and maps (and slices, but those can be created from arrays too).
Slices in Go and Golang The basic difference between a slice and an array is that a slice is a reference to a contiguous segment of an array. Unlike an array, which is a value-type, slice is a reference type. A slice can be a complete array or a part of an array, indicated by the start and end index.
As mentioned in Making slices, maps and channels:
The built-in function make takes a type
T
, which must be a slice, map or channel type, optionally followed by a type-specific list of expressions.
It returns a value of typeT
(not*T
).
The memory is initialized as described in the section on initial values.
For instance, for Slice type
make([]T, length, capacity)
produces the same slice as allocating an array and slicing it, so these two expressions are equivalent:
make([]int, 50, 100) new([100]int)[0:50]
So here, make
creates the slice, and initialize its content depending on the zero value if the type used (here int
, so '0
')
You can see more about the need of keeping new and make separate in Go: why would I make() or new()?
Dave cheney just wrote a good article: "Go has both make and new functions, what gives ?"
Although
make
creates genericslice
,map
, andchannel
values, they are still just regular values; make does not return pointer values.If
new
was removed in favourmake
, how would you construct a pointer to an initialised value ?Using
new
to construct a pointer to aslice
,map
, orchannel
zero value works today and is consistent with the behaviour ofnew
.For the confusion they may cause,
make
andnew
are consistent;
make
only makes slices, maps, and channels,new
only returns pointers to initialised memory.
First difference is type: make(T, ...)
always returns type T
, whereas new(T, ...)
always returns type *T
. That tells you that they are very different.
new
works for all types, and dynamically allocates space for a variable of that type, initialized to the zero value of that type, and returns a pointer to it.
One way to think of it is that
result = new(T)
is always equivalent to
var temp T result = &temp
(in other words you can do the same thing that new
does by defining a variable of the given type, not initializing it, and then taking a pointer to it.)
make
works as a kind of "constructor" for certain built-in types (slice, map, or channel).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With