Luca, thanks for your answerr
El viernes, 2 de febrero de 2024 a la(s) 3:06:17 p.m. UTC-3, Luca Pascali
escribió:
> you forgot the \n in the printf format string
>
> without it, next is written right after the end of the printf
>
>
> Psk
>
> Il ven 2 feb 2024, 17:56 Juan Mamani ha scritto:
>
>>
Kurtis, thanks for your reply.
El viernes, 2 de febrero de 2024 a la(s) 2:12:55 p.m. UTC-3, Kurtis Rader
escribió:
> I think you're being confused by the lack of newlines in the output. Add
> "\n" to the end of the printf format.
>
> On Fri, Feb 2, 2024 at 8:56 AM Juan Mamani wrote:
>
>> Hi ev
you forgot the \n in the printf format string
without it, next is written right after the end of the printf
Psk
Il ven 2 feb 2024, 17:56 Juan Mamani ha
scritto:
> Hi everybody!
>
> I was checking consistency behavior of fmt.Printf with some basic
> samples. And for my surprise never expected
I think you're being confused by the lack of newlines in the output. Add
"\n" to the end of the printf format.
On Fri, Feb 2, 2024 at 8:56 AM Juan Mamani
wrote:
> Hi everybody!
>
> I was checking consistency behavior of fmt.Printf with some basic
> samples. And for my surprise never expected wh
Hi everybody!
I was checking consistency behavior of fmt.Printf with some basic samples.
And for my surprise never expected what I found.
My context:
OS: Linux, debian 8,9,10,11
Go version 1.21
What I was doing? Learning about fmt.Printf
Expecting fmt.Printf behavior be the same output for any
