Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pull] master from go101:master #38

Merged
merged 2 commits into from
May 11, 2024
+1 −1
Merged

[pull] master from go101:master #38

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d1e178d
Update method.html to fix typo
zlqpzww May 8, 2024
12ff0dd
Merge pull request #280 from zlqpzww/master
zigo101 May 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pages/fundamentals/method.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -429,7 +429,7 @@ <h3>Method Values and Method Calls</h3>
<p>
Wait! Why does the line <code>book.SetPages(123)</code> in the above example compile okay?
After all, the method <code>SetPages</code> is not declared for the <code>Book</code> type.
One one hand, this can be viewed as a syntactic sugar to make programming convenient.
On one hand, this can be viewed as a syntactic sugar to make programming convenient.
This sugar only works for addressable value receivers.
Compiler will implicitly take the address of the addressable value <code>book</code>
when it is passed as the receiver argument of a <code>SetPages</code> method call.
Expand Down
Loading