> you can probably read it as Invalid argument index or invalid use of
> argument index.
> Hope that helps
Thank you mb0, now it make sense. I'm not confident as Go user to guess
things like that.
Thank you Ian Lance Taylor. I have now quite a pile of Go must read texts,
when I end my day jo
On Fri, Oct 8, 2021 at 12:36 PM Kamil Ziemian wrote:
>
> 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.
You can send
On Fri, 2021-10-08 at 15:33 -0700, Kamil Ziemian wrote:
> Hello,
>
> I now read documentation of "fmt" package and in "Format errors" (
> https://pkg.go.dev/fmt@go1.17.2#hdr-Format_errors) we have
> Invalid or invalid use of argument index: %!(BADINDEX)
> Printf("%*[2]d", 7): %!d(BADINDEX
Hi Kamil,
you can probably read it as Invalid argument index or invalid use of
argument index.
Hope that helps.
On 10/9/21 12:33 AM, Kamil Ziemian wrote:
Hello,
I now read documentation of "fmt" package and in "Format errors"
(https://pkg.go.dev/fmt@go1.17.2#hdr-Format_errors) we have
Inv
Hello,
I now read documentation of "fmt" package and in "Format errors"
(https://pkg.go.dev/fmt@go1.17.2#hdr-Format_errors) we have
Invalid or invalid use of argument index: %!(BADINDEX)
Printf("%*[2]d", 7): %!d(BADINDEX)
Printf("%.[2]d", 7): %!d(BADINDEX)
I cannot understand
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 2021 o 00:53:11 UTC+2 Kamil Ziemi
> 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
Kamil,
Have you read https://go.dev/blog/errors-are-values by Rob Pike? Wrapping
my head around the concept that an error is simply a value returned from a
function was tremendously helpful when I had questions along the same lines
as yours.
--
You received this message because you are subscr
>
> I'm not sure what you mean when you say that io.EOF is not treated as an
> error. io.EOF is an error: it implements the error interface, and is
> returned as the error value by methods such as Read.
I am mediocre at best at programming and I'm quite a picky person, so I
just have a problem w
Kamil,
A Go interface implements a particular behavior. For example, io.Reader is
the interface that wraps the basic Read method.
type Reader interface {
Read(p []byte) (n int, err error)
}
The outcome of the Read method ranges from good to catastrophic failure.
The outcome is
On Wed, Oct 6, 2021 at 2:35 PM Kamil Ziemian wrote:
>
> I currently read about "io" package and again I read that "io.EOF" is not
> treated as error, since it is what you expect to end file, which is almost
> tautology. At the same time it satisfies error interface and is created
> busing error
Hello,
I currently read about "io" package and again I read that "io.EOF" is not
treated as error, since it is what you expect to end file, which is almost
tautology. At the same time it satisfies error interface and is created
busing errors.New function.
I understand why this is done, doing i
Ah, I missed the bit where it says "Flag syntax is xyz (set)
or -xyz (clear) or xy-z (set xy, clear z)." You're quite right, there's a
much simpler way:
https://play.golang.org/p/upupUQUcsR8
On Saturday, 4 September 2021 at 20:51:53 UTC+1 kziem...@gmail.com wrote:
> Thank you for your answer a
Thank you for your answer and opinion Briana Candler.
I ask about unset only because of the cryptic text, at least to me, in the
description of RE2 (https://github.com/google/re2/wiki/Syntax). From
practical point of view, your solutions look good.
I try to google about changes in examples in Go'
On Sun, Aug 29, 2021 at 1:08 PM Kamil Ziemian wrote:
> Thank for explanation, but I don't understand "But how many bits do you
> need to represent 0? The question is malformed as there are no set bits in
> the used representation of 0.". Why this is malformed questions? When I
> think of coding 1
15 matches
Mail list logo
