►
From YouTube: 2021-03-17 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
Yes,
I'm
functional
now
all
right,
so
I
guess
there
are
two
main
things
we
probably
want
to
talk
about
today.
One
is
our
the
capture
macro,
sorry,
not
the
macro,
but
the
character
clause.
I
went
through
the
discussion.
That's
happening
on
t
line
so
maybe
want
to
go
over
that
a
bit
I
okay,
there
haven't
been
an
update
since
I
looked
at
it.
I
guess,
which
is
nice
and
then
also
chris
are
working
on
diagnostics
and
you
probably
want
to
discuss
how
we
want
to
work
things.
C
A
So
one
second,
I
will
share
my
screen
or
chris.
If
you
want
to
do
it,
go
for
it,
you
should
do
it
and
all
right.
I
will.
C
B
D
A
D
D
So
mutable
here
immutable,
borrow,
occurs:
here's
the
enclosure
and
then
we're
kind
of
pointing
at
this
thing
which
causes
it
to
be
mutable.
C
C
A
A
A
B
B
B
A
B
I'm
debating
about
including
there's
something
repetitive
about
saying
p
is
captured
because
if
it's
used
here
when
you've
underlined
p
and
like
the
but
otherwise
I
don't
know
what
to
say
like
what
is
the
noun
we
can
use.
That
makes
it
clear
otherwise,.
B
So
too,
and
usually
it's
a
pretty
short
path,
so
it's
not
like
so
difficult.
Do
we
want
to
take
some
notes
somewhere?
Are
you
taking
notes.
B
B
Yeah,
I
have
a
open
issue
to
rework
the
diagnostics
api
so
that
you
can
say
like
order
diagnostics
and
give
it
an
order,
and
then
it
will
do
what
it
has
to
do
to
make
sure
that
they
they
read
in
order
but
sort
of
like
if
it
works,
it'll
display
them
as
one
snippet
and
if
not
it'll,
break
them
out,
but
nobody
ever
did
it.
I
don't
even
know
if
it'd
be
a
good
idea.
I
still
think
it
is,
but.
A
So
we
had
p
is
captured
here
with
captured,
because
of
use
here.
P
dot
x
is
mutated
because
if
he's
here
or
just
beautiful
rope,
let's.
B
A
A
I
was
going
for
the
second
line
right,
so
we
have
two
lines
right,
so
we
have
the
first
one,
which
is
where
we
see
the
use
of
the
path
right,
which
is
p,
is
captured
because
of
use
here
and
then
yes,
second,
one
is
p,
is
borrowed
mutably
because
of
used
hair.
Yes,.
C
A
So
I
guess
one
one
more
question
I
have
not
regarding
diagnostics,
but
before
we
jump
into
closure
clauses,
so
on
the
other
other
pr
that
was
open,
which
was
to
replace
our
closure
captures
with
lawyer
main
captors,
there
was
a
comment
about
hashing.
A
The
owner
id
one
second,
I
will
I'm
just.
A
A
A
This
thing
so
yeah,
so
we
had
the
third
runner
not
being
used
so
instead
of
hashing,
can
we
just
put
an
azert
back
if
we
can
make
sure
that
that's
the
same
thing
or
do
you
think
hashing
is
the
preferred
choice.
A
There's
no
obvious
place
for
the
assert,
so
there
actually
you're
right.
We
don't
actually
do
this
this
way,
so
we
can't
put
another
okay,
never
mind
enough.
Okay,.
A
B
Does
what
so
every
def
id
it
corresponds
to
some
path,
which
is
canonical
like
the
module
path
essentially,
and
so
local
def
path,
hash?
What
that
says,
it
doesn't
hash
the
def
id,
because
that
itself
is
not
stable
across
builds,
that's
just
a
number,
but
it
hashes
the
path
to
which
the
def
id
refers.
So
if
you're.
A
A
A
A
B
C
D
E
B
That's
right,
but
it's
not
too
hard,
especially
if
you
have,
I
think,
multi-span
closures
you,
you
basically
need
to
figure
out.
Is
there
a
block
in
the
closure
body
and
if
there
is
a
block,
you
should
be
able
to
add
sort
of
immediately
after
this
open
brace
of
the
block,
let
underscore
equals
semicolon
yeah
right.
B
If
there
isn't
a
block,
then
you
want
to
add
brace,
let
underscore
equals
and
you
need
to
add
a
closing
brace,
but
we
actually
do
have
the
span
of
the
closure.
So
the
closing
brace,
probably
just
wants
to
be
inserted
at
the
kind
of
last.
B
Yeah,
exactly
okay,
I
think
that
will
just
work.
The
only
thing
is
there's
some
kind
of
bug,
or
I
think
we
don't
support
presently
multi-spin.
B
B
The
alternative
is
to
replace
the
entire
closure
body,
which
is
actually
not
that
bad,
it's
just
a
messier,
looking
diff
for
the
user,
but
you
could
yeah.
You
could
get
the
closure
body
now
that
I
think
about
it.
That's
what
you
want
to
do.
I
guess
you
want
to
get
the
body
of
the
closure
and
look
at
its
span
or
look
whether
it's
a
block
and
if
it's
a
block,
insert
the
let
underscore
equals
in
the
very
beginning.
C
B
C
C
A
B
A
Yeah,
that's
what
I
was
thinking
as
well
as
like
when
you
have
two
different
ones,
which
is
one
is
just
like.
A
closing
verse
will
feel
very
weird.
B
A
A
B
A
Yeah,
I
think
that
would
be
nice.
We
can
just
leave
I'll
leave
it
on
the
ticket
and
I'll
leave.
This
span
suggestion.
B
Well,
here
open
this
open,
this
link.
C
B
A
Yeah,
I
think
so
I
think
it
was
in
one
of
the
type
description
prs.
They
were
using
something
similar.
B
B
B
Yeah,
so
here
you
see
the
first
line,
if
let
okay
snippet
that
gets
the
text.
Snippet
is
like
the
string
and
then
it
does
a
suggestion.
But
if
you
this
one's,
maybe
incorrect
because
I
guess
it
might
not
compile.
If
you
look
at
the
the
last
example,
it
kind
of
puts
all
that
together.
The
last
link
I
sent.
B
A
B
Put
the
snippet
zoe
just
stick
that
you
might
want
to
do
something
similar.
I
don't
know,
but.
A
A
Boring:
okay,
what
you
want
to
do
is
f
for
providing.
B
A
A
A
A
A
It's
something
around
regions
not
being
resolved
so
yeah
reason
region
really
should
not
perform.
So
I'm
assuming
we
are
calling
fold
sooner
than
we
should
is
what
my
guess
would
be,
because
we
do
this
before
right
back
and
dive
check.
D
C
A
Basically,
full
dies
the
moment
it
goes
into
super.
B
A
A
B
Yeah,
you,
don't
you
don't
need
the
regions,
though
you
should
use
a
different
function.
C
A
B
Yeah
I'm
searching
resolve
vars
if
possible,
that's
what
it's
called.
A
I
see
okay,
that
is
all
right.
I
will
leave
a
comment.
A
A
Yeah,
do
you
guys
have
anything.