Adamcolton at 18:11, 29 June 2017

2017-06-29T18:11:42Z

@@ Line 12: / Line 12: @@
 Most of the time this works fine, if you're really memory conscious about that overhead, you can use pointers to slices and maps.
 == Not Go 2 ==
@@ Line 18: / Line 28: @@
 === Package fulfills interface ===
 A package behaves much like a struct - it's almost syntactically equivalent. For dependency management, it would be nice to use packages to fulfill interfaces.

Adamcolton: Created page with "What I would want in Go 2 == Go 2 == === Append to nil map === should create the map, particularly useful in a struct. ==== Or better nil for defaults ==== It would be even ..."

2017-06-29T16:37:07Z

Created page with "What I would want in Go 2 == Go 2 == === Append to nil map === should create the map, particularly useful in a struct. ==== Or better nil for defaults ==== It would be even ..."

New page

What I would want in Go 2
== Go 2 ==

=== Append to nil map ===
should create the map, particularly useful in a struct.

==== Or better nil for defaults ====
It would be even better if no built-in types could be nil.

What is currently a nil slice would just be slice with both len and cap of 0. Same thing with a map - there is no nil map, just an empty map.

Most of the time this works fine, if you're really memory conscious about that overhead, you can use pointers to slices and maps.

== Not Go 2 ==
(stuff that could be added without breaking backwards compatibility)

=== Package fulfills interface ===
A package behaves much like a struct - it's almost syntactically equivalent. For dependency management, it would be nice to use packages to fulfill interfaces.

Go2 - Revision history

Adamcolton at 18:11, 29 June 2017

Adamcolton: Created page with "What I would want in Go 2 == Go 2 == === Append to nil map === should create the map, particularly useful in a struct. ==== Or better nil for defaults ==== It would be even ..."