►
From YouTube: It's time to Go! Episode 2
Description
Informal chat about the Go programming language.
In this episode we are addressing https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/issues/86.
A
I
we
are
here
at
the
it's
time
to
go,
call
or
talk
about
google
and
we
forgot
to
record
it
unfortunately
from
the
beginning,
but
we
remember
now
and
we
will
go
through
what
we've
discussed
today
so.
A
To
converting
enum
to
strings
because
we
believe
that
there
is
a
problem
with
phenoms
where
we
can't
it's,
we
can't
use
the
same
names.
I
think
that's
that's
correct.
Let's
say
you
can't
use
the
same
enough
names
without
having
them
as
unique.
Is
that
a
good
description,
or
would
you
describe
it
differently.
B
So
all
all
enums
in
a
single
package
have
to
be
named
differently,
like
the
values
for
the
nums
have
to
be
named
differently,
because
the
values
share
the
namespace.
They
don't
belong
to
a
particular
in
enum.
Basically,
and
that's
just
annoying,
you
can't
have
two
enums
with
the
same
value.
If
you
rephrase
it
that's
the
thing,
so
we
decided
a
long
time
ago
that
we
want
to
change
this
and
to
a
string
and
just
use
validation
on
top
of
that
string.
B
Instead
of
in
doing
the
validation
for
us,
and
we
can
actually
do
a
better
job
with
validation.
A
B
If
you
want
to
default,
I
meet
the
the
value
I
need
the
the
field
or
in
your
yaml,
so
do
not
specify
network.
If
you
want
default,
you
don't
specify
an
empty
string
if
you
want
default
and
we
can
disambiguate
or
distinguish
between
these
two
by
having
the
optional
there.
So
we
track
if
the
field
is
present
or
not
it's
a
new
feature
that
was
added
a
year
ago,
so
to
proto3
it
wasn't
available.
C
A
And
also
like
because
the
nums
were
like,
I
think
they
default
naturally
to
zero
because
they
are
integers.
I
think
right
and
now
we
have
to
also
apply
the
default,
because,
like
said,
we
cannot
have
like
that
empty
string,
design
people,
so
we
need
to
also
implement
like
the
defaults
of
what
this,
if
the
user
does
not
pass,
it
then
once
they
before.
A
And
here
we
implement
functions
to
basically
apply
the
defaults
and
we
didn't
have
a
function
that
would
apply
the
default
to
a
string,
pointer
or
a
pointer
to
a
string,
and
this
is
basically
what
we
got
from
protocol
buff
from
protobuf
after
we
regenerated
the
protocol,
the
protobuf.
A
A
B
And
I
suggest
you
currently
all
the
fields
the
defaulting
happens
in
the
order
of
the
fields,
so
please
move
it
above,
so
that
we
maintain
the
order.
B
B
No,
what
we
need
is
we
need.
B
To
do
this
in
a
few
a
few
more
places
everywhere,
the
network
was
used
where
your
nam
was
used.
Sorry.
A
B
B
B
Yeah
this
is
the
observability
server.
Okay.
Now
I
think
this
was
a
separate
type
for
this.
The
observability
listen
cf,
but
then
we
also
need
to
look
at
what
other
addresses
are
there
to
find
the
matching
networks.
B
A
C
A
B
C
B
A
C
C
C
C
A
A
A
B
Yeah,
maybe
there's
several
that
use
the
same.
Listen
api,
struct,
yes,
api.
C
B
You
need
to
run
the
tests,
something
might
actually
fail.
Also,
we
have
the
that.
B
C
B
C
B
A
A
C
A
C
B
B
I
think
radius
uses
the
empty
string
as
the
default
and
then
we
can
change
it
to
optional
to
disallow
the
empty
string.
Basically,
if
you,
if
you
look
for
that
string,
validation
and
yeah
in
the
profile,
just
look
for
an
empty
string.
Basically,
two
double
quotes
yeah.
This
needs
to
be
changed
to
optional.