On Mon, 3 May 2021 at 20:24, Øyvind Teig wrote:
> I see that, which is great. But I still don't understand why
> https://go2goplay.golang.org/p/S_5WFkpqMP_H (By *rog*, 29Apr2021
> 23:52:05) seems not to print "Client 2".
>
That's because to try to emphasise the arbitrariness of the producers (an
On Tue, May 4, 2021 at 1:16 AM Delta Echo wrote:
> > Not sure what "handle" means in this case.
>
> I want to know how this is implemented.
>
> At some point in the compiler, you have type erasure, and you have an
untyped language. From there on, it's a function pointer / label. And you
allow for
On Tue, May 4, 2021 at 8:03 AM 'Axel Wagner' via golang-nuts <
golang-nuts@googlegroups.com> wrote:
> Thanks :) At least I didn't overlook anything :)
>
fwiw, I also searched the spec and found nothing. I found that peculiar.
Recursive types require special treatment in type theory, so it is like
Thank you for this Go Blog post and even more for encourage me to read the
Go spec. C++ give spaces a bad name and teach me to avoid them.
sobota, 1 maja 2021 o 20:16:45 UTC+2 wagner riffel napisał(a):
> On Sat May 1, 2021 at 11:12 AM -03, Kamil Ziemian wrote:
> > Can you guide me to some materi
On Sat, May 1, 2021 at 1:28 PM Jesper Louis Andersen <
jesper.louis.ander...@gmail.com> wrote:
>
> func g() string {
> s1 := "a"
> s2 = s1 + "b"
> return s
> }
>
>
Errata: it should have been `return s2` rather than `return s`. I hope I
didn't confuse people too much.
--
Hello.
I recently found that "A Tour of Go" is in polish with is my native
language. Polish is parochial language of polish nation, which is very
verbose, have incomprehensible rules, full of rare letters and for English
speaker probably impossible to pronounce in correct way. Basically if
En
Dnia 2021-05-04, o godz. 08:08:26
Kamil Ziemian napisał(a):
> Hello.
> Just on first page. There is "mozesz", when it should be "możesz", with
> I don't know where to start. I try to google answer, but found nothing.
> Can anyone guide me?
https://github.com/golang/tour/blob/master/TRANSLATE
That's a totally reasonable thing to do, and in fact co-developing two
modules the way you are describing is probably one of the best use cases
for `replace` directives. Though, keep in mind that replace directives
won't actually be honored by any packages which depend on yours (in this
exampl
The package go/types, which can represent Go types,
represents recursive types with cycles.
It also has explicit code to detect and handle such cycles when comparing
types
for identity, assignability, etc.
Go compiler represents type with a different package, internal to Go
compiler which is no
Dziękuję bardzo. Thank you.
I never used App Engine before, so I have one more question. Polish version
of "A Tour of Go" and this file tell you how to make it localized from
scratch, which is not very reasonable. It will make more sense if I join
people that make current versions and help with
10 matches
Mail list logo
