►
Description
A
B
A
A
A
A
B
The
proposal
in
there
was
to
do
some
more
sophisticated
handling
of
to
string
instead
of
just
doing
a
plain
strings,
actually
doing
a
try-catch
around
it
and
then
doing
something
more
sophisticated
with
the
object.
The
current
proposal
was
to
simply
say,
couldn't
to
string
your
two
string
failed
or
two
string
through
an
exception,
but
there
was
some
discussion
in
there
about
doing
some
object.
Inspection
on
that
case
I
to
me.
That
seems
like
it
bridge
too
far
because,
like
what
are
you
doing,
throwing
in
a
two
string
like
this?
Don't
do
anything
with
two
string.
B
Leave
it
alone,
please
so
I'm
happy
with
the
current
version
of
it.
I've
been
is
just
when
he's
gone
opinion
on
this
on,
though
so
I
I'm
I'm
happy
with
the
current
implementation,
which
is
simple
and
doesn't
swallow
the
error,
but
actually
and
doesn't
put
it
in
a
outside
of
the
stack
but
gives
you
some
information,
and
it's
our
fault
as
well
for
inspecting
this
object
in
the
first
place
and
if
you
look
at
chrome,
I
suspect
Firefox
as
well,
but
it
doesn't
inspect
the
object.
B
C
C
An
error:
how
can
we
be
sure?
How
can
we
print
something
safely,
so
this
problem
of
printing
something
safely
has
been
brought
up
a
lot
of
times
already
and
we
don't
have
a
genetic
utility
to
do
this.
Okay,
so
my
point
in
there:
it's
not
showing
the
exception
that
has
been
thrown.
It's
not
nice,
okay,
even
if
the
string
is
throwing
an
exception
and
try
to
print
that
exception
as
well.
C
B
And
that
one
of
the
one
of
the
responses,
so
that
was
that
it
might
not
actually
be
a
real
exception.
It
could
be
any
random
object,
that's
being
thrown,
but
that's
I
mean
this.
This
is
my
point
about
there's
a
rabbit
hole
here
that
we
could
go
down
with
a
really
sophisticated
implementation,
and
my
question
is:
is
it
worth
it
for
this
case,
because
this
is
a
very
specific
case
now
I'm
not
aware
of
anything?
That's
is
similar
in
our
code
base.
C
Okay,
I've
said
I,
don't
remember
the
issues,
but
I
have
seen
this
subject
being
moved
along
on
being
talked
in
a
lot
of
times:
okay,
I'm
fine
with
the
current
implementation
I'm
just
you
know.
Oh
this
seems
a
little
bit
C
so
because
that's
if
you
have
that
error
got
the
bug,
bat
in
production,
that's
not
my
only
that's
my
only
problem
because
the
two
strings
that
failed
an
exception.
You
girl
you,
you
have
left
with
more
or
less
nothing.
C
E
B
C
Yeah:
okay,
that's
why
I'm
saying
good,
but
this
subject
has
been
brought
up
other
times,
just
I'm,
not
it's
also
the
fact
that
you,
if
you
start
doing
these
type
of
things,
we
already
have
a
problem
in
there
in
that
specific
part
of
the
code
base,
that
those
exceptions
do
not
do
not
cross
the
system.
We
already
have
a
duplication
in
place,
so
it
will
get
I'm.
Just
I
just
want
some
bad
keep
setting
bad
presidencies
on
this,
but
that's
my
only
my
only
concern.
B
A
B
Was
one
of
those
and
I
think
he's
just
outlined?
Why?
And
that
sounds
like
a
reasonable
approach,
but
so
I
guess
the
question
now
is:
do
we
do
we
move
forward
with
this
simplistic
version,
with
a
an
ideal
version
down
the
track,
or
do
we
just
leave
it
as
it
is
because
it's
not
really
hurting
anyone?
It's
just
kind
of
messy
if
you
do
a
custom
to
string
and
then
do
the
idea
later
on
so
jump
straight
to
the
ideal
and
reject
this
interim
step
or
accept
this
as
an
interim
step.
D
A
A
D
B
B
A
A
A
C
Emerged
I
just
recorded
something
from
the
that
was
discussed
briefly
and
the
VM
summit
in
San
Francisco
at
nodejs
I'm,
not
summit
in
divine,
so
I'm
just
reporting
what
was
discussed
in
there.
There
was
a
problem
on
an
API
to
start
gathering,
adoption
and
feedback,
so
people
can
try
it
out
and
see
what
to
do
how
that
works,
because
there
is
a
there's,
a
missing
feedback
link
at
this
point,
so
one
of
the
option
that
was
discussed
was
dropping
the.
C
B
They're
a
link
to
the
notes
that
were
taken
at
the
VM
someone
that
was
doing
a
Google
Doc,
but
there
was
a
lot
of
discussion
about
this.
A
lot
of
keenness,
I
think
on
behalf
of
most
members
there
to
get
this
happening
just
because
there
was
a
barrier
to
adoption.
I
see
Jeremias
is
was
raised
an
objection
to
this.