►
From YouTube: 2021-03-26 RFC 2229
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Fair
enough,
okay,
starting
recording,
now,
okay,
oh
I
see
I
did
already.
That
was
the
main
thing
I
was
going
to
tell
you
is
that
you
want
that
method.
Yes,.
B
I
I
think
I
looked
into
it
a
bit.
I
didn't
find
any
exact
relevant
things,
but
I
didn't
spend
too
much
time
when
I
did.
If
you
click
it.
Oh
I
by
that
I'm
okay,
so
I
search
for
where
it's
used.
B
It
was
hard
to
find
a
little
where
it
was
probably
being
used
for
these
specific
closures,
but
I
think
if
we
go
and
trade
selection,
you
might
be
able
to
find
it,
because
we
had
a
lot
of
obligation
issues
in
the
past
when
rox
ended
the
are
on
jenny,
the
inference
variable
stuff.
B
B
B
What
I
was
going
for,
but
I
think
something.
B
B
A
The
first
line
is
this
clause:
you
can
make
a
dummy
or
sorry
cause,
you
can
make
a
dummy
cause,
the
parameter
environment,
and
that's
that
should
be.
You
should
have
that
floating
around
somewhere
you're
going.
B
B
B
A
B
A
A
B
B
B
B
Look
at
this
so
over
the
next
weekend
kind
of
I
supposed
to
go
ahead.
A
B
This
is
just
like
this
is
the
diagnostic
thing
that
we
were
talking
about
last
week.
I
think
oh,
this
is
so
when
okay,
so
whenever
we
do,
this
is
just
like
the
debug
logs
have
something
broken,
and
that
had
sent
me
on
a
sorry,
a
long.
B
Very
cool
all
right
yeah,
let's
just
make
sure,
there's
no
issue
that
don't
have
a
milestone
on
them.
I
don't
think,
there's
anything
specific
yeah,
okay,
so
yeah
you
probably
want
to
then
look
into
compiler
efficiency.
B
A
Like
we
could
literally
put
a
printf
or
something
like
that,
I
think
that
would
be
ideal
where
we
just
dump
the
size
of
before
and
after
size
of
every
closure.
And
then
we
scrape.