Re: [go-nuts] Various questions about posts from The Go Blog

Hi Kamil, FWIW, you probably would be better off going through the official module tutorials: "Tutorial: Get started with Go" -- https://go.dev/doc/tutorial/getting-started.html "Tutorial: Create a Go module" -- https://go.dev/doc/tutorial/create-module Those are listed at the start of the

Re: [go-nuts] Various questions about posts from The Go Blog

On 26 Mar 2023, at 20:01, Kamil Ziemian wrote: But I cannot understand why in the blog post we have in go.mod file require rsc.io/quote v1.5.2 so "rsc.io/quote" is considered direct dependency, while go.mod produced by Go 1.20 give me

Re: [go-nuts] Various questions about posts from The Go Blog

Jan Mercl you right that only TestHello is broken, but it is still broken. As I said, the fact that such simple code in not portable is disturbing. I guess most of the code is tested on OS with English as the main language, at least code for this blog post seems to be, so you can guess what

Re: [go-nuts] Various questions about posts from The Go Blog

The only broken thing in the code below is the TestHello function. rsc.io/quote uses rsc.io/sampler where the Hello func (https://pkg.go.dev/rsc.io/sampler#Hello) is documented to return a localized string by default. Localized, in the sense of respecting the user's locale. That is not compatible

Re: [go-nuts] Various questions about posts from The Go Blog

Hello, According to the law that any change can break your program/workflow, I want to mention that code shown in "Using Go Modules" https://go.dev/blog/using-go-modules is broken in funny way. Consider code below package hello import "rsc.io/quote" func Hello() string { return

Re: [go-nuts] Various questions about posts from The Go Blog

Hello, I try to learn how to use Go modules and Google PhD, recomended me Go blog post "Using Go Modules" https://go.dev/blog/using-go-modules. It seems a bit outdated and I want ask, if it so, should I use other source? I should mention that I like Go blog. Example of things outdated,

Re: [go-nuts] Various questions about posts from The Go Blog

On Mon, Jan 24, 2022 at 6:38 AM Kamil Ziemian wrote:, > > I have one more think to say about Go blog post "Why generics?". Again, > nothing really important. > > In the section "Generic data structures" in the second counting from the end > code example we have line. > > *pn = (E){val: v} > It

Re: [go-nuts] Various questions about posts from The Go Blog

Hello, I have one more think to say about Go blog post "Why generics?". Again, nothing really important. In the section "Generic data structures" in the second counting from the end code example we have line. > *pn = (E){val: v} It is commented by the sentence "Notice the type argument E to

Re: [go-nuts] Various questions about posts from The Go Blog

Hello, Since with release of Go 1.18 we will have Go's generics, I started a preparation tour around Go blog and YouTube. And here is one suggestion and one unimportant comment of mine about blog post "Why Generics?" (https://go.dev/blog/why-generics). This post is in my opinion very

Re: [go-nuts] Various questions about posts from The Go Blog

I agree with Kamil. Go is young and growing. Committing to keeping at least the "official" blogs updated will help us on-board new gophers and get them productive quickly. I appreciate the effort the Go team puts into the blogs and documents. How can we make it easier and better? Leam On

Re: [go-nuts] Various questions about posts from The Go Blog

"Blog posts should really be viewed as a snapshot that is valid when they're published (that's why they contain a date)" I agree, but since page that you are referring contains numbers of links to Go Blog posts with description "The official blog of the Go project ,

Re: [go-nuts] Various questions about posts from The Go Blog

Blog posts should really be viewed as a snapshot that is valid when they're published (that's why they contain a date) The guides under https://golang.org/doc/#getting-started however should be kept up to date with the latest releases On Monday, November 8, 2021 at 11:24:48 AM UTC+1

Re: [go-nuts] Various questions about posts from The Go Blog

"Technically that behaviour is still available via GO111MODULE=auto. Go 1.16 changed the default from "auto" to "on"." Thank you for that information. It is surprisingly hard to me to learn basic of Go and Go tools, when things don't works as described. I found few another places where "Using

Re: [go-nuts] Various questions about posts from The Go Blog

This is probably silly thing, but I will write it down just in case. I mentioned before Go blog post "Using Go Modules" ( https://go.dev/blog/using-go-modules), we first write a function func Hello() string { return "Hello, world." } and test for it which basically check condition Hello()

Re: [go-nuts] Various questions about posts from The Go Blog

Technically that behaviour is still available via GO111MODULE=auto. Go 1.16 changed the default from "auto" to "on". On Saturday, October 30, 2021 at 11:17:05 PM UTC+2 kziem...@gmail.com wrote: > Hello, > > I don't have energy today to read Go language spec or learning how UTF-8 > works, so I

Re: [go-nuts] Various questions about posts from The Go Blog

Hello, I don't have energy today to read Go language spec or learning how UTF-8 works, so I decided to make a look at Go blog post "Using Go Modules" (https://go.dev/blog/using-go-modules). I have a simple question: is this post up to date? I guess not, here is my reason why. According to it

Re: [go-nuts] Various questions about posts from The Go Blog

On Tue, Sep 7, 2021 at 3:40 AM Kamil Ziemian wrote: > > In the post "Concurrency is not parallelism" by Andrew Gerrand > (https://go.dev/blog/waza-talk) under the paragraph starting with "To clear > up this conflation, Rob Pike gave a talk at Heroku’s Waza" in my browser is > big blank space.

Re: [go-nuts] Various questions about posts from The Go Blog

On Tue, Sep 7, 2021 at 12:40 PM Kamil Ziemian wrote: > In the post "Concurrency is not parallelism" by Andrew Gerrand > (https://go.dev/blog/waza-talk) under the paragraph starting with "To clear > up this conflation, Rob Pike gave a talk at Heroku’s Waza" in my browser is > big blank space.

Re: [go-nuts] Various questions about posts from The Go Blog

Hello, In the post "Concurrency is not parallelism" by Andrew Gerrand (https://go.dev/blog/waza-talk) under the paragraph starting with "To clear up this conflation, Rob Pike gave a talk at Heroku’s Waza" in my browser is big blank space. I believe that that I can see rectangle in it, with

Re: [go-nuts] Various questions about posts from The Go Blog

On Wed, Aug 18, 2021 at 1:30 AM Kamil Ziemian wrote: > > I guess it should say "any number type", but I'm not 100% sure. Am I right? > > Thank you for the answer. I'm not good at computer science, so I'm often > can't decide is this mistake or is there some subtlety that I'm missing. Thanks for

Re: [go-nuts] Various questions about posts from The Go Blog

I guess it should say "any number type", but I'm not 100% sure. Am I right? Thank you for the answer. I'm not good at computer science, so I'm often can't decide is this mistake or is there some subtlety that I'm missing. Small mistake and typos are quite common in blogs and talks and I am

Re: [go-nuts] Various questions about posts from The Go Blog

On Tue, Aug 17, 2021 at 9:13 AM Kamil Ziemian wrote: > > I'm now rereading post "Constants" and in the last section "Numbers" there is > a text > > BEGINNING > Therefore, although they have different implicit default types, written as > untyped constants they can be assigned to a variable of

[go-nuts] Various questions about posts from The Go Blog

Hello, I'm now rereading post "Constants" and in the last section "Numbers" there is a text BEGINNING Therefore, although they have different implicit default types, written as untyped constants they can be assigned to a variable of any integer type: var f float32 = 1 var i int = 1.000 var u