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.

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

book: change println to fmt.Println entirely #155

Open
Delta456 opened this issue Aug 3, 2020 · 4 comments
Open

book: change println to fmt.Println entirely #155

Delta456 opened this issue Aug 3, 2020 · 4 comments

Comments

@Delta456
Copy link

Delta456 commented Aug 3, 2020

Hey! Thanks for writing such an awesome book but I had noticed that you have used print and println for printing to stdout. These function use should be discouraged as its for bootstrapping and it can be removed whenever Go Team wants to.

I prefer we should switch to fmt.Println() and fmt.Print().

EDIT: I saw the opening pages which has a note about it but this should be scrapped and can be given in Some Special Topic.

@Delta456 Delta456 changed the title book: change println to fmt.Println book: change println to fmt.Println entirely Aug 3, 2020
@go101
Copy link
Owner

go101 commented Aug 3, 2020

Yes, the two builtin functions are only used in the starting chapters (before the "Code Packages and Package Imports" chapter) to a void explaining packages and importing in those chapters.

can be given in Some Special Topic.

Do you mean move this note down somewhere in the "Introduction to Source Code Elements" chapter?

@Delta456
Copy link
Author

Delta456 commented Aug 3, 2020

Yes or we can make a chapter for C interpolation/bootstrapping.

@go101
Copy link
Owner

go101 commented Aug 3, 2020

Maybe, showing the note in a special style would be better.
There are many notes in Go 101 articles.
They deserves a style which could attract more attention.

@Delta456
Copy link
Author

Delta456 commented Aug 3, 2020

Yeah

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants