►
From YouTube: 2021-02-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).
B
Where
are
we
well?
We
need
to
discuss
the
timeline
from
an
updates
perspective.
I
think
this
week
and
next
week
are
going
to
be
slow
because
we
basically
have
all
our
deliverables
and
like
midterm
exams
next
week,
so
things
are
going
a
little
slow,
I
think
hopefully
we'll
have
at
least
one
beer
for
you
and
okay,
a
bunch
of
bug
fixes
will
be
like
got
approved
last
week,
so
there
will
be
slowly
emerging
and
this
week.
B
And
that's
yeah
and
I
think
the
key
things
that
remain
after
this
will
be
diagnostics,
which
I
don't
expect
to
be
too
long,
is
just
need
to
figure
out
some
time
to
work
on
it.
We'll
have
patterns
which
roxanne
is
working
on
and
I
think
the
concerning
one
would
be
clone
and
order
trades.
A
I
was
thinking
okay,
this
is
annoying
sorry,
I
I'm
I'm
thinking
we
were
talking
about
my
milestones
on
the
on
the
zoolop
I
was
thinking.
Maybe
I
should
create
some
or
maybe
we
can
actually
create
them
in
the
repo.
B
B
I
think
I
think
you
can
just
create
mile
appear
as
a
milestone
or
something
or
sorry
an
issue
as
a
milestone
or
oh,
if
you
go
on
issues,
you
can
create
a
milestone.
There's
like
the
on
the
top
right
section,
there's
labels
and
milestones.
Oh.
A
A
Damn
it
that's
so
annoying
I'll
just
make
you
host.
I
guess
that's
the
easiest
thing
to
do.
A
B
B
This
will
merge
sometime
soon.
I
was
looking
at
the
queue
it's
somewhere
down,
but
hopefully
in
the
next
couple
days
it
gets
merged.
There's
a
bunch
of
things
above
it.
B
We
have
two
out
of
three
things
of
our
migrations
implemented
and
the
only
thing
that's
left
in
the
segment
destructors
so
drove
hopefully
sometime
by
the
end
of
next
week,
should
be
able
to
get
to
this.
B
B
When
we
fake
the
information
about
b
it
ends
up,
then
this
whole
thing.
This
is
going
to
be
not
being
an
issue,
because
this
is
going
to
be
a
problem
with
similar
to
when
you
have
light
underscore
patterns,
so
we
can
just
use
the
same
rule,
which
is
just
back
off
on
to
fall
back
onto
upwards
mentioned,
so
I
think
this
this
can
be
dealt
with
pretty
easily.
So
this
is
not
that
this
is
yeah.
B
This
is
the
issue
to
use
the
new
structure
mint
captures
everywhere
instead
of
using
closure
captures
and
upper
capture
map
so
well,
one
main
benefit
is
that
any
people
won't
use
the
old
structure
to
do
things,
and
you
know
we
keep
using
the
new
structure
everywhere
and
it's
also
duplicate
information,
so
it
will
free
up
some
how
much
memory
we
use
and
at
the
same
time
it
will
reduce
the
size
of
the
incremental
cache
and
time
it
takes
to
actually
hash
the
cache
so
hash.
The.
B
It's
going
to
just
be
it's
a
straightforward
win.
I
think
this
is
done
if
I'm
correct
roxanne,
like.
C
Yeah,
like
I
took
a
look,
it
looks
pretty
good
to
me,
but
I
think
it
we're
still
hoping
I
mean
that
you
take
a
last
step
on
it.
Yeah.
B
I'll
I'll
I'll
do
it
and
then
we
can
create
a
vr
on
this
number.
D
Patterns
is
I'll.
Let
I.
C
Don't
know
it's
still
a
work
in
progress,
it's
been
giving
me
a
hard
time,
there's
been
a
few
issues,
but
I
think
I'm
hopefully
seeing
the
lights
out
of
the
tunnel.
So
I'm
focusing
on
this
this
week
and
hopefully
I
get
somewhere.
C
I
just
need
to
poke
it
some
more.
It's
just
like
trying
to
get
more
familiar
with
the
code
and
yeah
I'll.
Let
you
know
if
that
changes,
and
I
need
help,
though.
A
B
So
diagnostics
I
talked
about
already.
This
needs
to
be
get
done.
I
think
yeah.
The
main
thing
that's
left
after
is
just
figuring
out
how
you.
E
B
Yes,
we
also
need
to
do
a
macro.
Yes,
I
was
going
to
ask
about.
F
B
A
B
Sorting
function
and
we
can
just
sort
it
before
right
back
on
anything.
So
that's
not
a
concern.
B
B
B
F
B
A
D
A
B
A
No,
I
think
we
really
have
to
do
something
right.
I
was
going
to
say
that
we're
we're
refactoring
the
way
that
the
unsafe
checker
works
and
it
would
still
require
the
unsafe
keyword,
but
it's
still
just
really
wrong.
A
Do
that
operation
until
you
get
into
that
unsafe
block,
so
we
really
do
have
to.
B
So
like,
if
I
understand
correctly,
basically,
if
we
are
accessing
a
field
and
by
a
by
reference,
then
that's
basically
that
what's
going
to
be
an
issue,
so
in
that
case
we
truncate.
A
Yes,
so
it's
it's
similar
to
the
raw
pointer,
except,
except
that
you
need
to
consider
the
way
that
you're
referencing
it
as
well.
A
B
Yeah,
okay,
yeah,
so
I
think
that's
about
the
update.
How
would
we
introduce
the
capture
macro
and
would
they
use?
Will
this
end
up
so
like
defining
the
macro
is
not
hard,
it's
more
about.
How
will
it
get
included
and
how
the
ast
will
figure
like
the
mac
expansion
happen
as
part
of
like
the
parsing
and
asd
building
process,
if
I
understand
correctly,
so
how
would
we
like?
B
How
does
how
does
the
compiler
know
this
be?
How
define
this
macro
is
what
I'm
asking.
A
A
In
the
standard
library
we
just
have
to
think
about,
I
probably
need
to
ping
the
libs
team
or
you
can.
Someone
needs
to
ping
the
lib
steam
to
ask
like
where,
in.
A
It
should
go
okay
these
days,
I
think
we're
actually
putting
you
see
the
definition
I
wrote
there
yeah.
That's
we're
just
gonna,
pretty
much
copy
and
paste
some
code
like
that.
But
the
question
is
just.
F
B
B
You
have
no
idea
how
standard
level
is
organized
so
well.
F
F
B
B
A
B
B
B
A
A
B
With
that,
my
concern
with
that
is
so
trade
selection
runs
once
before,
and
once
after
no.
A
It
does,
but
you
don't
need
that,
there's
a
there's,
a
function
that
would
be
useful
to
you.
If
I
can
remember
what
it's
called
one.
Second,
if
all
we
want
to
know
is,
is
this
trait
implemented.
F
A
Search
around
it's
like
obligation,
colon,
colon,
new
or
something
yeah
I'll,
probably
I
can.
If
you
need
help,
I
can
find
you
something.
B
A
B
A
B
All
right
yeah,
I
think,
let's
discuss
milestones,
I
I
think
maybe
you
can
share
and
like
sure,
as
we
introduce
more
of
them.
A
Already,
let
me
regain
host,
how
do
I
do
that
other?
It
is
reclaim
host.
Okay
share,
I
have
to
say,
amazon
has
amazon.
Chime
is
like
this.
The
thing
we
use
internally
and
it's
fine
for
the
most
part,
it's
just
fine,
but
it
does
one
thing
super
well,
which
is
when
you
share
a
window
like
like
zoom
pops
up
this
inscrutable
dialogue.
A
That's
super
stressful
and
I
always
I'm
not
sure.
If
I'm
clicking
on
the
right
window
chime,
does
it
much
better,
not
that
you
care
all
right
there
we
go.
I
think
I
got
the
right
one.
Yes,.
D
F
A
B
B
B
A
They
don't
need
a
date
yet,
and
then
I
think
before
that
we
want.
We
wanted
to
have.
A
B
A
So
we
can
put
in
the
description
like
measure
size
of
new
closures
versus
old
closures.
I
don't
know
if
there's
anything
else,
we
need,
but
we'll.
A
Exactly
that's
why
we
have
a
milestone,
so
we
can
stick
things
in
it
and
then
the
next
one
is
like
migration
correctness.
Yes,
this
is
basically
have
we
tested
I'll,
just
call
it
migration
correctness.
Have
we
tested
that
migrations
are
working
and
have
we
fixed
them?
A
A
Oh
no,
why
did
it
reorder
them?
It's
annoying.
F
A
B
A
A
Yeah
too
many
tabs
that
gives
us
some
stuff
so
stabilized
for
new
addition.
B
B
A
Yeah,
I
think
what
we
should
do.
I
think,
let's
put
the
migrations
implemented
technically,
our
deadline
was
june
1st,
but
I
put
I'm
going
to
put
this
at
an
earlier.
We
may
want
to
move
some
of
our
deadlines
a
little
earlier
too.
I
don't
know
how
much
it
matters,
but
I'm
just
going
to
go
ahead
and
call
this
the
same
as.
B
A
Right
exactly
so,
why
separate
them
feature
migrations,
so
what
I'm
thinking
is-
and
it
seems
to
me
like
these-
are
the
deadlines,
but
we're
actually
going
to
get
there
much
faster.
I
think
right.
A
A
I
don't
know
whether
you
all
are
interested
in
writing
that
I
would
sort
of
love
for
you
to
write
it,
because
you
did
all
the
work
and
I
want
you
to
get
all
the
credit.
But
if
you
aren't
into
that,
that's
fine,
but
I
think
we
could
put
a
blog
post
on
inside
rust,
for
example,
sort
of
an
update,
saying.
B
B
Once
we
once
we
sort
of
fit
that,
I
think
we
should
fix
the
open
bugs.
E
A
A
Have
to
make
that
happen,
which
is
another
issue
we
should
add
to
the
list
that
says
we
probably
we
probably
want
them
to
test
it
with
the
feature
gate,
though
yeah
because
usually
like
moving
to
the
edition,
may
do
a
bunch
of
other
things
that
aren't
related
to
our
feature,
and
so
it's
not
the
best
test.
Okay,.
A
A
Is
this
some?
What
do
we
call
this
bug?
I
guess
all
right,
all
right
enhancement,
I
don't
know
whatever.
Who
cares
so
should
we
triage
and.
B
B
Go
on
can,
I
think,
go
in
the
we
can
filter
with
watson,
diagnostics
and
bug,
and
I
think
all
of
them
can
go
in
feature
complete.
B
A
B
B
Yeah,
oh
I
realize
I
haven't
looked
at
this
issue
and
sorry
that
the
comments
on
that
issue
so
sorry
that
took
me
a
polish
mindstone.
I
think
that
should
come
after.
We
have
gotten
testing
feedback
from
actual
people,
because
I
I
think
that
that's
going
to
be
somewhere
between
stabilization
and
feature
completeness,
is
what
someone
who
is
not
us,
who
is
using
this
feature,
thinks
and
what
they
think
can
be
improved
because
like
unless,
of
course,
there
are
things
that
we
okay,
so
polish
milestone
actually
might
be.
23
might
be.
B
One
of
the
issues
so,
which
is
2018,
is
also
feature
complete.
B
B
B
Okay,
so
this
is
again,
this
is
like
the
polish
milestone
that
I
think
this
can
go
in.
A
A
It
means
migrations,
are
complete
with
no
known
bugs
diagnostics
or
corner
cases
and
not
be
covered.
A
So
then,
there's
like
so
feature
complete
and
then
polish
complete,
which
is
basically
feature
everything
works.
A
B
A
No
known
bugs
migrations
work,
no
known
bugs.
A
Effects,
yes,
diagnostics
are
not
embarrassing.
A
B
D
A
A
A
B
So
I
think
I
had
talked
to
the
team
overall
seemed
like
maybe
end
of
second
week
of
march.
You
could
be
pretty
close,
but
this
again
is
high
level.
I'm
not
100
sure
how
much
like
we
have
looked
into
our
coming
deadlines
from
a
school
perspective,
because.
B
E
Feature
complete
yeah
but
like
yeah.
A
Yeah,
I
think,
but
let's
let's,
let's
review
at
the
end
of
the
month
or
something
we're
not
close
enough
to
say
yet.
I
think
so
drop
order.
In
my
opinion,
drop
order
is
probably
polish.
A
And
I
could
even
see
an
argument
for
saying:
drop
order
is
undefined
by
the
compiler,
and
you
know
if
you're,
relying
on
that,
whatever
anyway
yeah
but
match
or
is
always
considered
a
use
of
the
place.
This
is
feature
complete.
I
think
right.
Yes,.
B
A
So
there
we
go
so
now.
Some
of
these
have
no
bugs,
but
that's
okay,
we
don't
know,
there's
no
real
work
items
that
are
worth
tracking,
except
like.
A
Yeah
we'll
make
an
issue,
I
guess
a
crater
run
to
test
migration,
and
then
I
think,
there's
I
don't
know-
is
this
in
this
milestone,
there's
probably
a
bug
for
like
write,
a
blog
post
to
encourage
public
testing.
A
B
A
A
B
B
C
B
I
think
once
chris
does
has
gets
time
to
work
on
diagnostics.
Three
more
will
close.
F
A
Oh,
this
is
really
great.
This
is
like
by
far
the
most
organized
project.
I've
ever
worked
on.
It's
fantastic.
B
A
Okay-
and
I
think
you
already
know
this,
but
you
know,
keep
pinging
me
if
you
have
things
from
yeah
with
you
I'll
I'll.
Do
that
all
right
all
right!
So
thank.
B
A
B
B
It's
it's,
the
top
part
all
right
figure
out
how
to
leave.
I
guess
that
will
stop
really.