Re: [go-nuts] What is a ordinary and exceptional error?

and developer > often overlap - hence "devops"). But it's a pretty self-consistent view > that can answer a lot of questions about good error handling and messages. > > >> >> I struggle to think of a scenario where it would be better to *not* allow >&g

[go-nuts] Re: Go FAQ needs updates or not?

nion. Best regards, Kamil piątek, 29 września 2023 o 23:31:59 UTC+2 Kamil Ziemian napisał(a): > Ok, there is one thing connected to Go FAQ that I don't like. > > In section "When did Go get generic types?" we read "See the language spec > <https://go.dev/ref/sp

Re: [go-nuts] What is a ordinary and exceptional error?

; nil. If a nil pointer is found that means the structure is corrupted. > Probably due to a programming bug. Exceptional errors are those which may > make it unsafe to continue execution. In which case calling panic() may be > the only sensible course of action. > > On Fri, Sep 29

[go-nuts] What is a ordinary and exceptional error?

Hello, In Go FAQ we read "We believe that coupling exceptions to a control structure, as in the try-catch-finally idiom, results in convoluted code. It also tends to encourage programmers to label too many ordinary errors, such as failing to open a file, as exceptional.", " Go also has a couple

[go-nuts] Re: Go FAQ needs updates or not?

generics description in Go Spec. I would propose to add some quationary note about that to Go FAQ, but this is only my humble opinion. Best regards Kamil piątek, 29 września 2023 o 22:21:35 UTC+2 Kamil Ziemian napisał(a): > Hello, > > I read Go FAQ again and I'm start to think th

[go-nuts] Go FAQ needs updates or not?

Hello, I read Go FAQ again and I'm start to think that few minor things may needs some update. It is only my humble opinion and I'm not even true programmer, only hobbist, so if you disagree, you are probably right. "What is the purpose of the project?" This section starts "At the time of Go's

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

Best regards, Kamil sobota, 29 lipca 2023 o 19:50:51 UTC+2 Kamil Ziemian napisał(a): > "The confusion may come from the fact that a list of forbidden built-in > operations is immediately followed by a list of (mostly) allowed operations > that illustrate the original rule?" >

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

s, function and method >>> calls and receive operations can appear in statement context. Such >>> statements may be parenthesized. […] The following built-in functions are >>> not permitted in statement context: >>> >>> This is IMO very clear about tho

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

>>> I think it might make sense to file an issue about this, though in >>> general that conversion is deprecated anyway and gets flagged by `go vet` >>> (and `go test`) because it is not what's usually expected. So I'm not sure >>> how important i

[go-nuts] Re: Amateur's questions about "Go lang spec"

sion from integer to string gives you UTF-8 representation of code point described by value of the integer? Or maybe it is indeed representation of integer described by UTF-8 specification? Best regards, Kamil czwartek, 28 października 2021 o 19:33:27 UTC+2 Kamil Ziemian napisał(a): >

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

I really understand the generics parts of the > spec myself. > > On Sat, Jun 10, 2023 at 7:13 PM Kamil Ziemian wrote: > >> This is not a complaint, but a reflection. I have read, as careful as I >> can, the half of the Go Spec and if I didn't learn how parametric >

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

is not a typo > > https://go.dev/issue/24451 > > - sean > > > On Sat, Jun 3, 2023 at 10:05 PM peterGo wrote: > >> It's a simple typo. Send in a fix. >> >> peter >> >> On Saturday, June 3, 2023 at 4:07:15 PM UTC-4 Kamil Ziemian wrote: >> >

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

On Sat, Jun 3, 2023 at 1:40 PM peterGo wrote: > >> >> Kamil Ziemian, >> >> // list of prime numbers >> primes := []int{2, 3, 5, 7, 9, 2147483647 <(214)%20748-3647>} >> >> The variable prime is a list of some prime numbers starting with the &g

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

ards Kamil czwartek, 4 maja 2023 o 16:38:50 UTC+2 Kamil Ziemian napisał(a): > You convince me to your point Axel Wagner. At the same time if we look at > examples in Go Spec, I think their can be improved. > "A0, A1, and []string > A2 and struct{ a, b int } > A3 and int A4

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

is the very first step. And it's not always trivial. For example, > `==` on `float64` is *not* reflexive. It seems obvious that NaN == NaN > *should* hold from how it's spelled - but it doesn't. > > So, I disagree that the examples should limit themselves to cases where

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

I make guess that it should be something like "struct{ a, b *A5 } and struct{ a, b *B5 }" Of course it my just be that I'm just stupid. Feel free to inform me that indeed I have no idea what is going on in the Go Spec. Best regards, Kamil czwartek, 4 maja 2023 o 12:20:35 UTC+2

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

but at the same time humble me saying that there is any mistake in the Go Spec is something that I shouldn't do. Best regards, Kamil poniedziałek, 8 listopada 2021 o 10:59:23 UTC+1 Kamil Ziemian napisał(a): > Thank you Jan Mercl, now I start to understand this rule. > > Best > Kamil &

Re: [go-nuts] Help me study resources or guides

n in Go. They are important, but since are the last Addition with big "A" to the language, you should leave them to the end. At least in the my opinion. Best regards, Kamil Ziemian wtorek, 2 maja 2023 o 18:52:56 UTC+2 Rajesh Pandian napisał(a): > HI Nyilynn, > > I have watched

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

the > user's locale. That is not compatible with your test function > expecting to always get the same string regardless of locale. That's a > bug. > > On Sun, Mar 26, 2023 at 7:47 PM Kamil Ziemian wrote: > > > According to the law that any change can break your prog

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

t fact that some code of this type is not portable between OS with different languages is a bit disturbing. Best regards, Kamil niedziela, 26 marca 2023 o 19:36:59 UTC+2 Kamil Ziemian napisał(a): > Hello, > > I try to learn how to use Go modules and Google PhD, recomended me Go blog &

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

2 o 23:56:46 UTC+1 Ian Lance Taylor napisał(a): > 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 structu

Re: [go-nuts] With Go support of Generics I don't sure If interfaces are really about methods (behavior)

In the past that was idea to introduce new concept to Go, it was called "contract" if I remember correctly. With it we would write type myNumber contract { int | float64 } Along the way they realize that contracts are just interface with few additions, so we ended where we are. Also it means

Re: [go-nuts] Re: clarifying Go FAQ: Is Go an object-oriented language?

d no.". So true question is: who is asking and how detailed answer he or she needs? Best regards, Kamil czwartek, 24 listopada 2022 o 12:44:56 UTC+1 Kamil Ziemian napisał(a): > I will start with cautionary tell. At one of his public talks Bjarne > Stroustrup in some way, admited that

Re: [go-nuts] Re: clarifying Go FAQ: Is Go an object-oriented language?

was just about which labels applies where, I would probably shrug and go do more important things. But, I consider it a case of "Let them hear you message" to use this slogan, and I happy to spend some of my time expleining people who ask what I understand about Go. For the same reaso

Re: [go-nuts] Re: clarifying Go FAQ: Is Go an object-oriented language?

" Let me ask, because I'm genuinely curious: Why does it matter? The labels we apply to things do not affect their function. Perhaps it affects how we think about them. Is that it?" My point of view is that. In the moment when you learn the flow of language X, it doesn't matter. But, it is not a

[go-nuts] Re: clarifying Go FAQ: Is Go an object-oriented language?

"But I feel like programmers bringing their ideas from other less ambiguously object oriented languages like Java and C++ often have difficulty writing idiomatic Go." I personally think that Java and C++ are less ambiguously OOP, only because we informally define OOP language as "language that i

Re: [go-nuts] clarifying Go FAQ: Is Go an object-oriented language?

I think in the 1990s it was a debate if Lisp with Common List Object System (CLOS) is OOP language. The answer they arrive was something like that. "No, if your definition of OOP is based on C++. But, why your definition of OOP should be based on C++?" I think the same fits Go. Go is in many way

[go-nuts] Re: Go tour translation workflow

Hello, I'm coautor of Polish translation, I can only tell how it looks like from my perspective. "So, after all, what is needed is a link to the deployed Go tour with a new translation, right?" I would need to check that, since the other person take care of it. "However, what is the right way

[go-nuts] Re: Golang make coding very explicit. People should be warned !

I hope they will join Go community. sobota, 12 listopada 2022 o 04:51:10 UTC+1 mario.g...@gmail.com napisał(a): > I'm about to do a presentation of Go for some coworkers. I thought it > shoul be required to warn them about explicit code ahead ;-) > > I make it this evening. > > Take it and share

[go-nuts] Re: Will Go be discontinued?

If Google stop developing Go, I think we just need to fork main repo and start United Gophers Foundation. :D wtorek, 26 lipca 2022 o 17:01:17 UTC+2 richar...@gmail.com napisał(a): > Yeah, and GMail and Google Search: their days are numbered > > On Sunday, July 28, 2013 at 10:25:11 AM UTC-7 Starf

Re: [go-nuts] Re: Blog: Calculating type sets is harder than you think

This blog post is extremely interesting. I wish I have better background in type theory and in complexity theory, I would understand this text much better. Due to my work (C#, C++, and some trivial stuff) I have almost no time to follow development of Go, so I have question about "There are als

[go-nuts] Why is Go fun?

Hello, I lack a motivation to read Go spec (long story) and I seek few stories along the line "Go is fun", which it is, to motivate myself. Google didn't give me any results, maybe you can tell me few reasons, why Go is fun? I feel that it is fun, but can't tell why.

[go-nuts] Re: Information for gophers in Ukraine

g the away, please have a patience for us. Best, Kamil Ziemian niedziela, 27 lutego 2022 o 03:06:00 UTC+1 al...@pbrane.org napisał(a): > Yes, let's support everyone! > > If any gopher from the DNR or LNR is tired of their plight > being ignored and wants to chat with a frie

[go-nuts] Information for gophers in Ukraine

I live in Poland in city of Cracov (https://en.wikipedia.org/wiki/Krak%C3%B3w) and at this moment I have one free room in my flat. If some gopher from Ukraine need a place to stay for himself/herself or for they loved ones, just write to me. I will try to help as much as I can. Kamil Ziemian

[go-nuts] Re: Is Go good choice for porting graph based app?

"As a result I know, I currently try to kick this graph can down the road." Stupid me. It should be "As a result I currently kicking this graph can down the road.", only written in better English than mine. Best, Kamil niedziela, 20 lutego 2022 o 21:43:10 UTC+1 Kamil Ziem

[go-nuts] Re: Is Go good choice for porting graph based app?

I think they use a set schema, but I need to check. To be honest, I have a lot to do on my own now and people from this graph app are acting as they were wanting to sabotage my work. I think that they just clueless about consequences of their actions. As a result I know, I currently try to kick

Re: [go-nuts] Going thorough "Type parameters proposal" with Go 1.18 beta

gt;>> The concept was renamed to "defined type" in Go 1.9. I assume Ian >>> mistakenly used it out of habit. But just so you are not confused about the >>> terms when reading other material. >>> >>> And, I know that you asked to respect yo

Re: [go-nuts] Going thorough "Type parameters proposal" with Go 1.18 beta

for encoding those numbers into bytes. I don't think > you really need to know anything beyond that to understand the Go spec. > > On Tue, Feb 15, 2022 at 1:19 PM Axel Wagner > wrote: > >> >> >> On Tue, Feb 15, 2022 at 11:18 AM Kamil Ziemian >> wrote:

Re: [go-nuts] Going thorough "Type parameters proposal" with Go 1.18 beta

come from Robert Griesemer's talk "Typing [Generic] Go" from GopherCon 2020 (https://www.youtube.com/watch?v=TborQFPY2IM), whiteout it I would probably have no clue what may happen. I still can understand it wrongly, but it is my fault. I hope this is not too silly question. Best

Re: [go-nuts] Re: Why you can name variable or type parameter int or uint8???

After reading your answers, I was looking for Go gotchas and I find this. At the first look it looks promising, do you have opinion on it? http://devs.cloudimmunity.com/gotchas-and-common-mistakes-in-go-golang/ Best, Kamil niedziela, 13 lutego 2022 o 23:58:14 UTC+1 Kamil Ziemian napisał(a

Re: [go-nuts] Strange cases of type definitions that use "[]", Go 1.17 and 1.18beta2

h at me, I deserve it. I also try to laugh at myself. :) I have a lot to do in this week, so I maybe silent for few days. Best, Kamil poniedziałek, 14 lutego 2022 o 00:05:04 UTC+1 axel.wa...@googlemail.com napisał(a): > On Sun, Feb 13, 2022 at 11:23 PM Kamil Ziemian wrote: > >> &qu

Re: [go-nuts] Re: Why you can name variable or type parameter int or uint8???

Thank you Jason and Axel. I know that "nil" is predeclared identifier from watching talk on YT "Understending nil" (or something like that) and know that it can be redefined. But, due to my background I still struggle with such things in Go. Old habits die hard, nothing more. Thank you Axel, yo

Re: [go-nuts] Strange cases of type definitions that use "[]", Go 1.17 and 1.18beta2

e in the realms of the compilers and parsers. Sorry if my response are chaotic. I will try to be more systematic in answering in the future, but for a while my answers will be messy. Best, Kamil niedziela, 13 lutego 2022 o 23:21:24 UTC+1 Kamil Ziemian napisał(a): > "I think there i

Re: [go-nuts] Strange cases of type definitions that use "[]", Go 1.17 and 1.18beta2

"I think there is arguably a difference between generic functions and generic type declarations. In the former case, an argument name is rarely needed for the documentation, whereas in the latter case it's probably always needed. Though I'm not sure, really." I complain about, to make excuse fo

Re: [go-nuts] Does anyone gets automatic response from 944677...@qq.com?

o person >> that set up this auto replay? >> >> piątek, 11 lutego 2022 o 14:56:10 UTC+1 ren...@ix.netcom.com napisał(a): >> >>> Same issue. Some one set up auto reply to message threads. >>> >>> On Feb 11, 2022, at 6:36 AM, Kamil Ziemian wrote:

Re: [go-nuts] Strange cases of type definitions that use "[]", Go 1.17 and 1.18beta2

tf("varSI value: %v\n", varSI) > fmt.Printf("varSI type: %T\n", varSI) > } and give in both cases result > varSI value: [ ] > varSI type: main.someInterface I didn't find any way to assign some new value to "varSI", but this is alre

Re: [go-nuts] Strange cases of type definitions that use "[]", Go 1.17 and 1.18beta2

pe typeName [3]int No problem with that. But, from what I see, both examples works. Best, Kamil piątek, 11 lutego 2022 o 15:37:59 UTC+1 Jan Mercl napisał(a): > On Fri, Feb 11, 2022 at 3:13 PM Kamil Ziemian wrote: > > > "> type someDifferentInt[float64] int > > I can'

Re: [go-nuts] Strange cases of type definitions that use "[]", Go 1.17 and 1.18beta2

e (https://xkcd.com/1172/) and Go backward compatibility police is quite strong. I want to write another 5k+ issue about thing that cannot be improved. Best, Kamil piątek, 11 lutego 2022 o 14:47:07 UTC+1 Kamil Ziemian napisał(a): > Axel I agree that "But there is at least some pote

Re: [go-nuts] Does anyone gets automatic response from 944677...@qq.com?

Bad that this is not only my problem. Did anyone try to write to person that set up this auto replay? piątek, 11 lutego 2022 o 14:56:10 UTC+1 ren...@ix.netcom.com napisał(a): > Same issue. Some one set up auto reply to message threads. > > On Feb 11, 2022, at 6:36 AM, Kamil Ziemi

Re: [go-nuts] Strange cases of type definitions that use "[]", Go 1.17 and 1.18beta2

t some discussion about that and I remember that you yourself have doubts about it. Best, Kamil piątek, 11 lutego 2022 o 13:56:54 UTC+1 Kamil Ziemian napisał(a): > Thank you Jan Marcel. I see now that I wasn't precise enough. I understand > that '[' and ']' are just

Re: [go-nuts] Strange cases of type definitions that use "[]", Go 1.17 and 1.18beta2

"Just accept it and carry on", it will be valuable. Best, Kamil piątek, 11 lutego 2022 o 13:38:44 UTC+1 axel.wa...@googlemail.com napisał(a): > On Fri, Feb 11, 2022 at 12:51 PM Kamil Ziemian wrote: > >> Can someone explain me, why compiler can't throw an error when i

[go-nuts] Does anyone gets automatic response from 944677...@qq.com?

Hello, I try to don't care about this response, but I see them one time to much. After most if not all my post here, I get email from 944677...@qq.com with title "自动回复: [go-nuts]: title of the thread" and content "这是来自QQ邮箱的假期自动回复邮件。 您好，我暂时无法亲自回复您的邮件。我将在最短的时间内尽快给您回复。谢谢。" Gmail translate it to "

[go-nuts] Strange cases of type definitions that use "[]", Go 1.17 and 1.18beta2

Hello, I should mention that I still don't read Go Language Specification (https://go.dev/ref/spec), due to my decision to first study Unicode and UTF-8, before reading it. It maybe strange thing to do, but I just how I need to deal with Unicode and UTF-8. Regardless of that I quickly check fe

Re: [go-nuts] Going thorough "Type parameters proposal" with Go 1.18 beta

that to learn UTF-8 I need to go learn about Unicode and I try to find time for it. Best regards, Kamil niedziela, 6 lutego 2022 o 03:47:36 UTC+1 Ian Lance Taylor napisał(a): > On Sat, Feb 5, 2022 at 4:27 PM Kamil Ziemian wrote: > > > > On the other hand this code compiled >

[go-nuts] Re: Is Go good choice for porting graph based app?

Thank you Sebastian Binet, I need to check more gonum project. You are right drv drv that Python is not true culprit here. Problem is that it seems a bad written code. Maybe after a while I will change my mind about it, but it looks bad right now. Here you have list of dependencies that came wi

Re: [go-nuts] Going thorough "Type parameters proposal" with Go 1.18 beta

oat is implicitly conversed to main.StringableVector[main.someFloat]. Answer to my previous questions was that []stupidFloat/[]someFloat is not of type StringableVector[stupidFloat] so it doesn't have method String() string. But in my poor understanding of Go, this code shouldn't compi

Re: [go-nuts] Going thorough "Type parameters proposal" with Go 1.18 beta

with generics" ( https://go.dev/doc/tutorial/generics) deals only with generic functions. I guess some additional tutorial about generic types will be good thing for people like me. Best regards, Kamil sobota, 5 lutego 2022 o 02:57:23 UTC+1 Ian Lance Taylor napisał(a): > On Fri, Feb 4, 2022

[go-nuts] Going thorough "Type parameters proposal" with Go 1.18 beta

Hello, I title say, I download Go 1.18 beta (at this moment "go version go1.18beta2 linux/amd64") and I try to work through "Type Parameters Proposal" with it (https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md). This thread is about thing that I can't co

Re: [go-nuts] Is Go good choice for porting graph based app?

14:26 -0800, Kamil Ziemian wrote: > > Hello, > > > > I was handed proof-of-concept app written in Python. It seems > > underdeveloped, buggy and running it first time is a pain, because of > > dependencies. Basically it need to read some graphs stored in JSON > >

[go-nuts] Is Go good choice for porting graph based app?

Hello, I was handed proof-of-concept app written in Python. It seems underdeveloped, buggy and running it first time is a pain, because of dependencies. Basically it need to read some graphs stored in JSON files and manipulated them accordingly and write them to JSON files again. It seems that

[go-nuts] Re: Optimizing GoAWK with a bytecode compiler and virtual machine

I will try to follow development of GoAWK. czwartek, 3 lutego 2022 o 22:38:46 UTC+1 ben...@gmail.com napisał(a): > Recently I switched (so to speak) my GoAWK interpreter from using a > tree-walking interpreter to a bytecode compiler with a virtual machine, and > got a noticeable performance boo

Re: [go-nuts] Why Go allow function with unused arguments?

n't be answered by looking at this correct function. For my money, answers lies in place to which you send function with given signature, it decides what and why passed function signature is. I maybe wrong about that. Best regards, Kamil poniedziałek, 31 stycznia 2022 o 12:40:08 UTC+1 Kamil Ziemi

Re: [go-nuts] Why Go allow function with unused arguments?

bout this 3 or 4 breaking changes. Best regards, Kamil niedziela, 30 stycznia 2022 o 21:09:46 UTC+1 kortschak napisał(a): > On Sun, 2022-01-30 at 12:01 -0800, Kamil Ziemian wrote: > > Hello, > > > > This is a question from ignorant in the meters of compilers and > > medio

[go-nuts] Why Go allow function with unused arguments?

guess it will be a long time before I can go back to learning proper Go. I read FAQ and I didn't remember answer to this question from it. This is my excuse for asking this question. Best regards, Kamil Ziemian -- You received this message because you are subscribed to the Google Groups

[go-nuts] Re: Anyone else writing an interpreter with Thorsten Ball?

Thank you for the feedback! piątek, 28 stycznia 2022 o 20:40:40 UTC+1 timphar...@gmail.com napisał(a): > It's very well-explained and the code's easy to read. And you can build on > it. I've been able to modify his code to my language spec, use syntactic > whitespace instead of braces, utf8 ins

Re: [go-nuts] Go 1.18, generics and fuzz testing

Thank you for information. There is so many things about Go and its tool chain that I need to learn and think about. Best regards, Kamil czwartek, 27 stycznia 2022 o 01:22:36 UTC+1 Ian Lance Taylor napisał(a): > On Wed, Jan 26, 2022 at 4:17 PM Kamil Ziemian wrote: > > > >

[go-nuts] Go 1.18, generics and fuzz testing

Hello, I accidentally initialize go.mod files for both tutorial on generics (https://go.dev/doc/tutorial/generics) and for fuzzing (https://go.dev/doc/tutorial/fuzz) with command > go mod init example/nameOfSubject and as a result both contains in respective go.mod file line > go 1.17 In the ca

[go-nuts] Re: Anyone else writing an interpreter with Thorsten Ball?

I found this books last weeks, on community page of different language and I consider buying them. But I have a lot thing to learn for Go with learning materials for free (unicode, UTF-8, Go spec, etc.), that I will probably postpone this book to the future. If you don't mind, I want to ask you

[go-nuts] Re: G 1.18, remarks on "Tutorial: Getting started with fuzzing (beta content)"

ot; to "The import statement of main.go should look like the following.". I like this more since first line on the file is "package main" and it is not shown in code example. Best regards, Kamil środa, 26 stycznia 2022 o 11:33:32 UTC+1 Kamil Ziemian napisał(a): > Ups, I just

[go-nuts] Proposition for Go proverb on generics: Write code, don't design types.

"Write code, don't design types." This statement is a title of the section of *Generics!* talk by Robert Griesemer and Ian Lance Taylor at GopherCon 2021, time 21:09 and while I start to try my hands with generics in beta of Go 1.18 I think that it l

[go-nuts] Re: G 1.18, remarks on "Tutorial: Getting started with fuzzing (beta content)"

nd to harsh about this tutorial. My English is not good enough to allow to me to write with desired tone. This only my suggestions and thoughts and I want to hear opinions of more competent people about this tutorial. Best regards, Kamil środa, 26 stycznia 2022 o 11:28:19 UTC+1 Kamil Ziemian n

[go-nuts] G 1.18, remarks on "Tutorial: Getting started with fuzzing (beta content)"

Hello, I have few doubts about "Tutorial: Getting started with fuzzing (beta content)" (https://go.dev/doc/tutorial/fuzz) and I want to hear your opinions on them. First few disclaimers. I new to fuzzy testing and while I like this idea, I'm to ignorant to say much about it. Also I already r

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

18 at syntax level is quite different than that presented in this blog post. Best, Kamil Ziemian poniedziałek, 24 stycznia 2022 o 12:47:11 UTC+1 Kamil Ziemian napisał(a): > Hello, > > Since with release of Go 1.18 we will have Go's generics, I started a > preparation tour aroun

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

ng 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? > >

Re: [go-nuts] Amateur question: when you should use runes?

ote: > >> >> >> On Mon, Nov 15, 2021 at 11:00 AM Kamil Ziemian >> wrote: >> >>> Hello, >>> >>> I read quite a few blog posts, articles, listen to nice number to talks >>> about strings, runes and encoding in Go. I now reading Go Language

[go-nuts] Amateur question: when you should use runes?

Hello, I read quite a few blog posts, articles, listen to nice number to talks about strings, runes and encoding in Go. I now reading Go Language Spec and I just stuck in the section about runes. I mean, it isn't hard as itself, but it raises to much questions to me. I decided that I need to le

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

t" (I'm >> quite sure that when I did this few years ago, this was the command that I >> used) I get >> >> hello.go:5:2: no required module provides package rsc.io/quote/v3; to >> add it: >> go get rsc.io/quote/v3 >> >> This is easy to so

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

it: go get rsc.io/quote/v3 This is easy to solve by running "go get rsc.io/quote/v3", but still annoying when you are going through this post. Best Kamil niedziela, 31 października 2021 o 00:29:57 UTC+2 Kamil Ziemian napisał(a): > This is probably silly thing, but I will wr

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

Thank you Jan Mercl, now I start to understand this rule. Best Kamil niedziela, 7 listopada 2021 o 19:34:41 UTC+1 Jan Mercl napisał(a): > On Sun, Nov 7, 2021 at 7:23 PM Kamil Ziemian wrote: > > > Can anyone give me explicit example when semicolon is omitted in > accordance to

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

syntax that will be used later > in the documentation, not the specific fields > and that is why you can not find "production_name" throughout the rest of > the docs. > However, for example, hex_digit is a in-docs Production built similarly to > what you are looking

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

rg/doc/), so I guess it should have note "If you use Go >> in version x.y.z or latter, some code may not work", but maybe I just think >> about it in the wrong way. >> >> From practical reason this particular thing isn't important, because >> go.mod fil

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

>From practical reason this particular thing isn't important, because go.mod file is the way to go (or at least this is what I read in the last week). Best Kamil wtorek, 7 września 2021 o 22:23:19 UTC+2 Ian Lance Taylor napisał(a): > On Tue, Sep 7, 2021 at 3:40 AM Kamil Ziemian wr

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

Thank you Patryk Węgrzynek for these notes. I often feel uneasy when things like "ways of comunications” are unclean to me just at the beginning of reading of text. I like have everything clear at start and you help me clear some mess in my head. Best Kamil pt., 29 paź 2021 o 16:00 Kamil Zi

Re: [go-nuts] Re: Amateur's questions about "Go lang spec"

Thank you Jan Marcel, now I understand this part of Spec. I now will go back to read rest of it. Best Kamil piątek, 29 października 2021 o 13:29:16 UTC+2 Jan Mercl napisał(a): > On Fri, Oct 29, 2021 at 12:53 PM Kamil Ziemian wrote: > > > > From what I understand about EBNF

[go-nuts] Re: Amateur's questions about "Go lang spec"

>From what I understand about EBNF production_name should be defined using EBNF notation in manner like below. production_name = something1 | something2 But I don't see such definition in Spec. Best Kamil czwartek, 28 października 2021 o 21:31:07 UTC+2 seank...@gmail.com napisał(a): > There

[go-nuts] Amateur's questions about "Go lang spec"

Hello, >From what I understand proper Gopher read at least one time "The Go Programming Language Specification" (https://golang.org/ref/spec) and now I need to read it too. I learn something of Extended Backus-Naur Form to understand it, so if I say something stupid beyond belief, I hope you w

Re: [go-nuts] Re: Questions about documentation of Go standard library

n I end my day job I will read them all and after that, I will "contribute" in this small way. Best Kamil sobota, 9 października 2021 o 02:46:56 UTC+2 Ian Lance Taylor napisał(a): > On Fri, Oct 8, 2021 at 12:36 PM Kamil Ziemian wrote: > > > > I found unimportant typo

Re: [go-nuts] Re: Questions about documentation of Go standard library

quot;, 7): %!d(BADINDEX) I cannot understand what "Invalid or invalid use of argument index" was intended to mean? Can anyone help me with that? Best Kamil piątek, 8 października 2021 o 21:36:11 UTC+2 Kamil Ziemian napisał(a): > Hello, > > I found unimportant typo in English

Re: [go-nuts] Re: Questions about documentation of Go standard library

Hello, I found unimportant typo in English part of the documentation of "fmt". How can I correct it? GitHub pull request or open issue "Unimportant typos in documentation"? I don't know how I should treat such unimportant typo. Best Kamil piątek, 8 października 20

Re: [go-nuts] Re: Questions about documentation of Go standard library

> The io.ReadAll function and the io.Reader interface Read method are not the same, don't conflate them. Thank you for stressing that point, but I don't think that I conflate them. Maybe I wrong, but I believe that many entries in "io" package share decriptions that states "A successful call ret

Re: [go-nuts] Re: Questions about documentation of Go standard library

;> closely syntax page of RE2 (https://github.com/google/re2/wiki/Syntax) >>>>>> and I still not sure if I understand one example from regexp package. >>>>>> >>>>>> In example in method func (*Regexp) FindIndex ( >>>>>> https://pkg

Re: [go-nuts] Re: Questions about documentation of Go standard library

(?m) set value of flag m to true and if I want set it to false I >>>> should write (?-m) or not? By default m should be false, but as example it >>>> is fine. >>>> >>>> As a side note, this regular expression is used in other examples, when >>>&g

Re: [go-nuts] Type Parameters Proposal, few unimportant questions

lenty materials about Go to read, listen and watch. > Thanks for the careful reading. I'm glad if I can help. :) Best Kamil piątek, 24 września 2021 o 19:34:43 UTC+2 Ian Lance Taylor napisał(a): > On Thu, Sep 23, 2021 at 10:07 AM Kamil Ziemian wrote: > > > >

Re: [go-nuts] Type Parameters Proposal, few unimportant questions

> > You can try out examples online in the go2 playground: > https://go2goplay.golang.org/ > Thank you Brian Candler for the information, I didn't know about go2 playground before. There are so many things that I need to learn about Go. I guess this comment is something that was missed. > I also t

Re: [go-nuts] Type Parameters Proposal, few unimportant questions

; more consistent with rest of the code would be "~int32 | ~int64". In section "List transform" (https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md#list-transform) in method func (lst *List[T]) Push(v T) we have lst.tail.next = &elem

Re: [go-nuts] Type Parameters Proposal, few unimportant questions

Thank you very much, now this sentence about type parameters with structural constraint is clear and I know that I basically get it right. Best Kamil pt., 10 wrz 2021 o 19:07 Ian Lance Taylor napisał(a): > On Fri, Sep 10, 2021 at 5:28 AM Kamil Ziemian > wrote: > > > > I

[go-nuts] Type Parameters Proposal, few unimportant questions

Hello, I try to work my way through "Type Parameters Proposal" (https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md). With my speed, I maybe and reading this very well written document before type parameters will be implemented in Go. xD Jokes aside, when I

[go-nuts] Re: Questions raised by "Understanding Allocations: the Stack and the Heap - GopherCon SG 2019"

Thank you Brian Candler. I finally need to learn EBNF, because it kill me when I tried to read Go Spec last time. Best Kamil wtorek, 7 września 2021 o 12:22:19 UTC+2 Brian Candler napisał(a): > > By the way, if someone can explain me what is going on with "println", I > would be gratefully. Th

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

up Fierfox data. Best, Kamil środa, 18 sierpnia 2021 o 18:13:31 UTC+2 Ian Lance Taylor napisał(a): > 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? > > > &g

[go-nuts] Questions raised by "Understanding Allocations: the Stack and the Heap - GopherCon SG 2019"

Hello, I often punch above my weight trying to understand various problem, so when I saw talk "Understanding Allocations: the Stack and the Heap - GopherCon SG 2019" by Jacob Walker (https://www.youtube.com/watch?v=ZMZpH4yT7M0), I cannot resist it. I'm basically compiler front-end user and not

  1   2   >