cybercyst/go
1
0
Fork 0
mirror of https://github.com/golang/go.git synced 2025-05-05 23:53:05 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Destroyed Rationales (markdown)

Matt Layher 2021-12-16 23:09:43 -05:00
parent d8310ac4e3
commit 5a4c4e787a
1 changed files with 0 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
Rationales.md

@ -1,37 +0,0 @@
# Introduction
This wiki entry will try to document the rationales behind some important language
decisions besides what's included in the Go FAQ and Effective Go.
# Language Features
### Why method receiver's base type cannot be pointer or interface?
Reference: https://groups.google.com/forum/#!topic/golang-nuts/aqTwXHaSC_Y
Go doesn't allow receiver's base type to be pointer to avoid possible ambiguity.
Suppose you have:
```
type T blah
type P *T
func (t *T) String() string { ... }
func (p P) String() string { ... }
var p P
```
Then the meaning of the expression ` (*p).String() ` is ambiguous, because it can refer to
both ` (*T).String ` and ` P.String `.
Go doesn't allow receiver's base type to be interfaces, because interfaces already have methods. (TODO)
### Select with closed channel
[Issue #11344](https://github.com/golang/go/issues/11344).
### Send to closed channel
[Issue #18511](https://github.com/golang/go/issues/18511).
# Memory Model
# Standard Library