►
From YouTube: Rust and WebAssembly Working Group Meeting 2019-05-16
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
B
Unfortunately,
not
stuff
at
work
has
kicked
up
very
hard
and
then
I
went
on
vacation
and
so
that's
been
complicated.
I
I
certainly
super
want
those
features
and
I
think,
like
the
general
design
conversations
that
we
already
have.
Are
there
yeah
I
guess
for
me,
like
the
it's
not
entirely
clear
from
what
we
bought
it
like
what's
already
been
discussed
on
the
issue,
exactly
what
like
the
bigger
contentious
portions
of
it
are
I,
don't
know
if
there's
like
particular
elements
that
we
think
need
a
little
bit
more
attention.
B
B
C
Kinda,
what
I
figured
as
well
in
terms
of
like
if
you're,
if,
if
like
you
and
rhaegar,
basically
are
cool
with
the
concept,
and
if
you
want
to
skip
it
and
just
see
the
general
idea,
I
think
that's
kind
of
we
just
needed
as
kind
of
just
buy-in
from
folks
who
work
very
closely
with
laws
in
pack.
We
should
be
good
to
go.
I
think
it'll
still
take
a
lot
of
time
to
implement
and
like
fully
unfold
review,
and
all
that,
so
this
is
just
more
of.
Is
it?
Does
it
sound
like
a
good
idea?
B
Alright
I
will
I
will
do
that
directly
after
this
meeting,
but
like
in
general,
like
as
I
said
when
I
was
like
put
this
on
hold
for
a
second,
the
general
direction.
I
think
matters
I
do
think
for
something
like
less
like
and
more
serve
might
have
a
couple
like
Devils
in
the
details
about
exactly
how
we
want
to
do
it
and
like
that
implementation
part
might
be
interesting,
but
yeah
we
can
I,
think
yeah
yeah.
A
A
I'm
sure
they'll
be
like
details
of
things
that
like
could
go
either
way,
for
example
like
if
we
want
to
use
a
pre-built
binary
that
just
does
local
serving
or
do
we
want
something
with
like
a
little
more
integration
where
we
actually
write
our
own
server
right,
maybe
get
something
out
of
that.
Like
that's,
also
the
kind
of
thing
that
I
feel
like
we
can
kick
down
the
road
to
some
degree
and
just
like
get
like
these
commands
introduced
doing
the
basic
thing
and
then
kind
of
move
on
from
there.
Okay,.
B
If
we
feel
cool
that
like
put
the
RFC
process,
because
sometimes
the
RFC
is
really
good
documentation
of
like
anyways,
if
we're
down
to
just
like
get
something
that
does
it
and
then
like
iterate
on
how
we're
doing
it,
I'm
super
fine
with
this,
certainly
the
user
facing
API
should
it's
is
relatively
straightforward
and
I.
Don't
anticipate
changing
regardless
of
what
we
would
do
with
the
implementation.
So
I
will
comment
this,
and
that
sounds
great.
A
A
My
my
thought
is
that
six
weeks
seems
maybe
arbitrary,
but
like
I'm
not
hitting
for
five
weeks
or
seven
weeks,
I
wonder
if
it
makes
sense
to
just
like
have
a
mechanism
of
like
grouping
like
essentially
milestones
across
repositories.
I'm,
just
saying
these
are
the
things
we
think
are
most
important,
and
so
we
should
work
on
getting
all
of
these
done
and
then
once
we
get
all
them
done
then
nominate
the
next
set
of
things.
A
B
I
definitely
think
that
make
sense
like,
even
though
there's
things
that
are
like
waiting
to
land
on
was
impact
like
the
next
set
of
things
like
if
someone
was
like
walking
into
as
impact
in
trying
to
decide
what
to
work
on.
But
the
big
chunk
is
like
it's
not
flagged
yet
and
we
probably
shouldn't
be
blocking
that,
and
so,
if
it's,
even
if
it's
not
like
exactly
six
weeks
like
that
type
of
planning,
I
think
it's
very
useful
and
we
definitely
see
a
ton
of
people
like
there
was
a
number
of
times.
B
A
A
B
Well,
there's
a
I'm,
gonna
say
vaguely
easy
fix,
but
I
can't
and
like
do
this
work,
but
the
work
to
do
is
relatively
straightforward
is
like
we
have
our
website.
We
have
one.
It's
like
update
the
landing
page
that
hasn't
happened,
so
we
should
do
it.
We
could
have
a
page
that
just
makes
that
API
call
and
dumps
it
on
a
website.
A
B
A
B
One
thing
I
will
say
is
like
we
do
have
all
of
this
kind
of
debts,
not
the
right.
Word
cuz,
it's
more
like
things
we
want,
but
just
haven't,
found
time
to
do
kind
of
around
website.
Stuff.
I,
don't
know
if
we
maybe
want
to
try
and
like
evangelize,
that
more
and
see
if
we
can't
collect
like
a
I'm
somebody
who
wants
to
join
who's
like
very
passionate
about
doing
website
stuff
with
webassembly,
we
should
have
like
at
least
a
large
portion
of
the
audience
being
front-end
developers,
yeah.
A
Yeah
I
think
I,
agree.
I,
think
the
thing
is
like
all
of
these
kind
of
outreach
pushes
require
someone
taking
a
leadership
role
to
like
guide
people
through
that
and
like
act
as
a
point
person
and
like
I.
Don't
really
have
the
cycles
myself
like
I.
Did
you
know
six
months
ago,
traveling
for
love
stuff,
so
I.
B
A
A
So
so
the
web
IDL
bindings
proposal
has
been.
Yes,
it
actually
expect
texture.
Anything
is
still
missing.
It's
just
the
explainer
that
was
kind
of
updated,
maybe
a
month
or
so
ago,
but
what
I've
been
doing
is
I've
been
starting
kind
of
the
planning
work
and
a
library
and
stuff
or
thinking.
How
can
we
take
waves
and
budget
and
from
being
like
this
vague
concept
of
future
compatible
with
the
web
IDL
bindings
into
okay?
A
A
Have
an
effect
on
like
the
kinds
of
things
we
do
with
like
dictionaries
and
stuff,
whereas
right
now,
dictionaries
select
web
IDL
dictionaries,
which
are
essentially
just
untyped
objects
that
have
certain
properties,
key
values
right
now.
What
we
do
is
we
create
J
objects
and
pass
them
over,
but
with
web
IDL
bindings
they're
more
like
structural,
where
you
would
synthesize
them
from
sequences
of
Latin
values,.
C
So
you're
thinking
like
we
should
I
see
I
hear
that
is
like
we
should
add
more
features
to
as
a
bunch
in
like
there
was
like,
if
you
return
to
pool
I
should
be
able
to
say
that
field
comes
from
this
thing.
That
field
comes
from
this
thing.
Basically,
the
the
whatever
you
expressions
language
or
a
deal
binding.
A
I'm
not
totally
sure
because,
like
we
have
to
balance
this
with
breaking
changes
and
stuff,
if
we
do
it
purely
additively,
maybe
maybe
oh
no
I
haven't
thought
about
it
all
the
way,
but
like
they're,
just
there
are
like
a
couple.
Impedance
mismatches
but
like
I,
know,
for
this
kind
of
initial
push,
it'll
be
basic
stuff
right,
like
it'll,
be
passing
strings,
I've
seen
objects.
B
I
was
just
slowly
filling
out,
my
section
so
I
think
mostly
for
Westpac.
It's
gonna
be
a
couple
of
things
that
got
bumped
and
then
I
have
like
a
couple.
Well,
one
of
them
might
actually
be
big,
but
we'll
see
so
the
things
that
got
bumped
like
the
big
one
that
I'd
want
to
the
next
brand
is
the
like
isomorphic
target.
The
one
like
was
impact,
builds,
knew
all
the
types
of
things
and
you
get
a
package
that
can
consid
node
and
for
all
the
types.
B
B
C
B
We've
been
pushing
this
NPM
install
wise
impact
thing
down.
The
road
and
I
could
be
nice
to
just
get
that
done
and
then,
like
the
one
that
I
think
might
be
big.
That
I
think
is
interesting.
That
I
just
saw
on
Twitter
I
guess
parcel
is
really
pushing
forward
on
its
like
press
webassembly
stuff.
Did
you
all
see
that
at
all?
B
B
Been
basically
no
idea,
I
literally
just
saw
it
like
30
minutes
ago
and
the
reason
I
saw
it
is
because
Twitter
showed
me
Shawn
Larkin,
responding
to
this
person
being
like.
Do
you
need
a
web
pack
example?
So
I,
replied
and
I
was
like
the
rest
was
and
docks
are
basically
a
would
pack
example
you're
fine
figure,
I'll
share
this.
B
Yeah
I,
don't
know
what
codes
sandbox
is.
It
looks
probably
like
a
you:
have
some
online
editor
thing
but
they're
doing
a
bunch
of
like
parcel
rust,
webassembly
stuff,
which
is
cool.
We
probably
should
retweet
this
from
Russell
Azzam
account
I,
don't,
but
I
am
not
entirely
sure
how
parcels
doing
it.
B
But
if
parcels
really
trying
to
push
on
this
and
there's
people
involved
like
I,
know,
Sarah
kind
of
and
she's
very
cool,
and
so
it's
there
might
be
an
opportunity
here
to
try
and
reconnect
with
that
parcel
team
and
get
them
into
the
docs
and
that
won't
be
I,
don't
think
a
very
large
technical
challenge,
but
it
will
be
a
fair
amount
of
work.
So
I.
C
B
C
B
A
B
See,
though,
yeah,
so
those
are
the
things
that
were
like
top
of
mind
for
me
and
then,
like
obviously
also
the
like
watch
and
serve
commands.
If
we
can
like
agree
that
we're
like
down
with
the
direction
I
think
we
can
do
that,
depending
on
when
we'd
want
to
like
get
the
next
sprint
out,
which
is
like
hilarious,
because
the
previous
print
is
not
out
yet
so
I'm
in
the
process
of
doing
that
today,
I,
don't
know
if
watch
and
serve
will
ship
in
this
one.
A
C
A
A
A
C
B
B
A
Is
like
basic
blocks
and
like
you
can
jump
anywhere
right?
There's
like
go
twos
whatever
and
JavaScript
obviously
doesn't
have
that,
and
so
you
have
to
kind
of
like
turn,
that
back
into
ifs
and
loops
and
stuff
like
that,
and
then
there's
like
cases
where
it
breaks
down,
and
you
have
to
kind
of
have
like
a
switch
statement
which
is
like
which
basic
am
I
going
to
go
to.
Essentially
in
the.
A
A
A
So
I
wrote
like
sketched
up
an
algorithm
in
a
notebook
somewhere
and
I
can
write
that
up
into
an
issue
and
compare
and
contrast
that
with,
like
maybe
adopting
real
uper
kind
of
thing
or
I.
Guess,
like
the
other
option,
is
to
like
hack
it
and
like
have
a
really
nasty
kind
of
special
case
for
different
values.
But,
as
you
might
be
able
to
tell
I,
don't
like
that.
C
Yeah
I
mean
I'm,
not
no,
that's
not
true.
Elvia
will
pick
up
support
for
multi-value
and
we
will
have
to
handle
this
within
like
actual
optimized
code
and
everything
so
yeah.
Let's,
let's
add
this
to
the
six-week,
sprint.
I,
don't
know
for
this
yet,
but
adding
multi-value
support
any
true
multi-value
support
dolores.
B
One
thing
I
can
say
is
like
once
the
stuff
that
we
have
listed
at
least
four
was
in
PAC
like
for
the
next
sprint
like
once
this
sprint
and
that's
print
lands.
I,
don't
really
know
what's
next
like
do.
We
have
thoughts,
like
usually
we've
been
like
just
pulling
out
this
huge
backlog
of
stuff,
but
we're
like
kind
of
getting
through
it.
A
B
A
B
A
C
Well,
yeah
anyway,
we
can
figure
it
out.
I
suspect
it
may
not
be
the
hardest
thing
in
the
world.
We
need
to
talk
with
webpack
and
kind
of
like.
What's
the
expected
way
to
do
that
and
I
feel
like
we
probably
have
to
get
by
some
management
if
you're
doing
stuff,
as
opposed
to
wasn't
packed
in
the
sense
like
the
generated
codes.
Probably
gonna
have
to
be
a
little
bit
different,
but
these
things
working
all
in
concert
together
and
if
it
only
works
with
web
pack
or
like
a
deep
bundler
target.
B
B
C
B
C
Want
to
make
sure
that,
like
the,
if
you
aren't
using
ie
11,
it
should
be
pretty
lightweight
in
terms
of
code
size
impact
or
what
you're
actually
doing
so
like
if
it
throw
if
you,
when
you
load
the
web,
page
download
the
J's
unconditionally.
That
would
be
no,
no
so,
but
if
otherwise,
if
it's
an
extra
50
bytes
to
say,
like
Emma,
do
I
support
assembly
fetch
that
or
fetch
this
and
I
think
my
default
make
total
sense.
Yeah.
B
I
think
the
cost
is
primarily
code.
Size
I
mean
one
thing
once
we've
run
out
of
things
on
what
wise
impact
to
do,
which
it's
probably
premature,
that
I'm
saying
we're
doing
that.
It's
like
we've,
never
really
been
concerned
with
super.
How
long
was
impacting,
except
for
when
we
were
originally
cargo,
installing
things
which
was
bonkers,
so
there
could
be
like
trying
to
optimize
build
times,
but
I
haven't
heard
people
complain
that
was
impact
takes
too
long.
Ever
since
we've
been
cashing
those
binaries.
A
A
B
Sounds
good
to
me
and
once
once
the
generate
and
wasn't
opted
pr's
land
like
one
of
the
reasons
the
generate
PR
is
so
large,
is
that
I
did
a
pretty
big
refactoring
so
that
using
like
dropping
in
new
tools
is
like
much
easier
and
we
won't
have
to
write
the
logic
for
each
one.
So
that
should
make
it
even
easier
to
add
something.
Like
wasn't.
Stan.
A
A
B
A
C
A
Like
again,
six
weeks
sprint,
it's
like
six
weeks
of
work
and
then
modulo
vacations
and
travel
and
conferences
and
stuff
right
and
I.
Think
it's
fine
I
think
the
important
part
is
probably
just
not
like
fighting
back
against
scope
creep
and
and
by
saying,
like
it's
six
worth
of
work
and
like
it
doesn't
matter
if
it
takes
ten
weeks,
but
like
it
doesn't
matter
that
we
don't
put,
you
know
a
year's
worth
of
work
in
one
sprint.
I
guess
we
have
some
sort
of
focus
absolutely.
C
A
B
I
am
so
I
finally
got
the
cargo
generate
PR
over
the
finish
line.
The
testing
is
not
great,
but
it
is
fine
and
I'm
sick
of
putting
it
off
and
yeah.
So
one
of
the
things
I
was
holding
it
up,
which
I
think
is
very
interesting
and
I
just
want
to
warn
you
all.
Since
you
also
work
on
the
project,
it's
something
happening
Clippy
and
there's
this
like
redundant
closure
lint.
B
That's
like
not
doing
the
thing
it's
supposed
to
do,
and
so
it
started
alerting
on
like
a
ton
of
super
old
code
and
wesen
pack,
and
so
I've
been
like
fighting
with
it
at
one
point,
I
just
friend
could
be
off,
and
so
finally
just
to
get
it
over
the
finish
line.
I
put
like
allow
warnings
on
there
talk
to
the
nation.
He
says
that
there
is
a
fix
in
the
works
and
they
may
backward
it
to
beta
anyways.
B
B
It
generally,
so
I'll
make
those
small
tweaks
land
that
and
then
there's
a
ton
of
super
awesome
like
bug,
fixes
and
like
little
things
that
have
landed
as
long
as
well
as
some
bugs
that
have
been
filed,
and
so
I'm
gonna,
try
and
figure
out
what
of
those
can
get
snuck
into
this
and
then,
ideally,
like
finish,
writing
up
a
change
log
and
try
and
get
it
out
tomorrow.
So
I've
already
opened
up
the
issue
in
the
PR
for
the
same
vlog
so
but
getting
those
things
over
there.
B
I
I
feel
that
I
should
have
broken
up
the
refactor
and
adding
the
generate
command
into
two
different
few
hours.
It's
very
very
foolish,
and
now
it's
like
two
thousand
lines
of
code
so
but
yeah
that's
what's
going
on
with
that
and
yeah
I
think
that's
the
full
of
it
anyways.
My
my
attention
is
on
flies,
infect
the
rest
of
the
day
and
tomorrow.
A
Flores
as
an
engine
goes
there's
the
new
release
if
the
support
for
futures
stood
futures
and
then
there's
also
again,
relating
to
profiling,
monitoring,
debugging,
etc,
there's
a
intrinsic
function
that
allows
you
to
count
how
many
jeaious
values
or
any
reps
are
in
the
West
engine,
and
so
you
can
use
this
to
help
tub
of
memory,
leaks
that
involve
holding
on
to
J
s
values.
And
then
you
can
also
use
this
to
rate
tests.
A
A
A
B
Thing
I
was
gonna,
say
it's
it's
not
that
it's
not
on
the
agenda,
but
our
updates
for
wasn't
bind
you
know.
Wasn't
pack
had
been
very
specific
and
we've
kind
of
already
discussed
that
I
guess
there's
kind
of
like
a
hole
here,
but
I
would
love
to
have
some
of
the
like
more
specific
features.
Stuff.
Just
like
discussed
in
this
meeting
about
glue.
B
Cool,
so
we
the
glue
going
to
adopt
one.
Do
you
anticipate
that
we
might
want
to
include
it
in
our
templates,
moving
forward,
mm-hmm
or
like
make
a
new
template?
That's
like
the
impact,
glue,
template
or
something
like
this
for
discovery
purposes.
I
tell
a
lot
of
people
that
glue
happened
and
they're
like
what
and
so
I'm
like
yeah.
A
B
A
The
thing
is
right:
now:
it's
like
they're,
very
utility
level,
libraries
and
like
I,
could
imagine
our
template
having
a
default
kind
of
like
hello
world
that
does
like
some,
you
know,
creates
a
little
Dom
that
says
hello,
world
or
whatever
right,
but
like
glue
right
now.
It
doesn't
have
any
of
those
facilities
for
working
with
the
Dom,
and
so
it's
like
coming
up
with
interesting,
but
also
small
examples
that
also
show
off
the
things
that
we
currently
have
support
for
is
like
well.