►
From YouTube: 2 August 2018 Meeting
Description
The Rust WebAssembly Working Group meeting from 2 August 2018.
A
B
Hey
thanks.
Everyone
for
coming
to
another
rusta
lives,
I'm
working
group
meeting,
so
today
is
the
day
of
the
release
for
the
2018
edition
preview
too,
and,
like
we've,
been
kind
of
trying
to
set
milestones
for
these,
you
know
releases
and
stuff,
but
like
obviously,
since
we're
not
actually
shipping
that
much
stuff
in
the
RUS
compiler
itself,
like
it's
more
just
like
a
suggestion
for
us,
but
like
the
big
thing
that
I
wanted
to
talk
about
for
this
meeting
was
like
planning
what
are
kind
of
suggested
goals
for
the
next
big
release
in
six
weeks.
B
B
And
so
that's
six
weeks
from
now
is
going
to
be
the
release
candidate
for
the
rest,
2018
edition
so
yeah,
but
before
we
dive
into
that,
just
a
note
on
our
C
triage,
the
Westin
buns
inheritance
RFC
has
entered
the
final
comment
period.
So
if
you
care
about
these
things
and
have
opinions
and
such
things,
this
is
like
the
last
chance
to
voice
your
concerns.
B
C
C
This
is
where
I
want
us
to
get
to
a
point
where
we
have
something
to
announce,
and
it's
like
probably
it's
like
mostly
okay.
We
would
like
with
some
manual
betting,
but
the
main
thrust
of
the
initial
announcement
I
would
see.
Is
let's
get
people
using
it
to
give
us
bugs,
and
then
we
fix
those
books
then
make
another
major
release
at
some
point.
So
the
idea
is
like
we're.
Gonna
push
something
out
there.
B
For
sure
and
huge
shout
out
to
was
it
da
da
and
I
forget
the
other
person
who've
been
like
just
hammering
on
website
stuff,
like
one
person
like
organize
all
of
the
issues
and
like
why
we
can't
generate
bindings
for
some
of
the
interfaces
and
then
another
just
started
like
implanting
tests
for
everything.
That's
awesome!
Okay!
B
C
Sort
of
didn't
this
acetate
publishing
it
so
publish
everything
else
just
to
just
to
have
it
on
Chrissa,
oh
I
would
not
I,
don't
see
it
currently
as
like
a
major
feature
like
I.
Don't
think
we
don't
have
a
lot
of
stuff.
That's
like
I
really
need
like
async
and
rust
right
now,
and
so
like
it's
ready,
ish
to
publish
and
I'm,
not
too
too
worried
about
it.
C
One,
so
that's
something
more
on
the
Y's
impact
side
of
things
like
I
would
say
for
the
release
candidate
like
the
wet
there
wasn't
pack
sealer
that
we
were
previously
talking
about
like
that,
should
probably
be
like
fully
fleshed
out
and
everything.
So
that
is
mostly
intended
to
just
be,
and
you
tell
that,
but
to
that
end,
I
do
think
that
we
want
it
relatively
finished
or
relatively
complete.
C
B
C
C
A
Think
it's
fine
like
in
wagon
pack,
we
already
have
commands
that
have
like
kind
of
like
test
implementations
in
there
like
not
polished,
but
because
it's
an
interface
that
we
expect
that
was
impact
will
will
always
give
you
and
just
we're
gonna
polish
it
up
under
the
hood
I.
Think
that's
fine
like
right
now,
likewise
impact
wise
impact
pack
and
publish
both
just
wrap
NPM,
which
is
like
not
ideal,
but
we
know
that
those
things
will
exist.
A
A
B
Right
now
is
like
very
much
prose
and
like
kind
of
like
almost
like
more
tutorial
II,
where
it's
kind
of
just
like
going
through
and
like
this
is
what
happens,
and
then
this,
and
that
and
like
that's,
really
good,
but
like
often
the
way
that
I
come
at
specifically
wasm
bind
Jen
documentation
is
like
I
want
to
look
up
exactly
like
what
is
the
thing
like?
What
does
this
actually
do
when
I
apply
it
to
this
struct
or
on
to
this
function?
A
A
Lists
like
there's
a
reason
listicles
are
so
freakin
popular
I
know
at
least
four
wasn't
by
doing
the
primary
questions
that
I've
gotten
from
it
when
I
present
on
it
or
just
like,
like
so
to
a
certain
extent.
Benjin
is
a
translation
tool,
so
I
want
to
be
able
to
look
up
one
thing,
either
on
the
rest
side
of
the
JavaScript
side
and
find
out
what
the
other
thing
it's
like.
What's
it
get
turned
into
you.
A
B
A
B
A
C
C
So
one
other
minor
thing
that
I've
been
dabbling
at
has
been
performance
in
the
sense
that
I've
been
using.
Like
wasn't,
mine,
Jenna
has
looked
a
lot
slower
than
I
thought
it
was
going
to
be,
it
should
be
like
blazingly
fast,
but
it
seems
to
be
kind
of
lagging
in
a
lot
of
cases,
and
so
some
of
that
is,
it
doesn't
seem
to
be
a
pervasive
problem
just
yet
so
I
guess
this
is
in
terms
of
performance
I.
A
One
thing
that
was
impact
can
do
is
time
how
long
each
step
takes
in
addition
to
how
long
the
entire
thing
takes,
and
that's
gonna
be
a
great
way
to
keep
track
of
that.
For
you
because
I
mean
I
think
what
are
the
big
things
that
we're
doing
for
this
kind
of
like
UX
overhaul,
is
what
the
goal
is
to
make
it
faster,
and
we
don't
have
a
bench
right
now,
but
we
should,
and
we
can
bench
the
steps
so
yeah.
B
A
B
B
C
B
A
So
six
weeks
is
like
both
a
long
time
and
not
a
lot
of
time.
I
think
the
next
two
releases
that
we
have
planned
for
wise
and
pack
are
pretty
well
defined.
Right
now
and
probably
will
ship
and
like
both
of
them
will
be
within
the
timeframe
of
like
three
to
four
weeks,
and
so
six
weeks
puts
us
on,
like
the
edge
of
like
whatever
ODOT
seven
would
be,
I,
think
and
I
guess
I'm,
not
really
entirely
sure,
where
I
think
we
want
to
go.
A
A
B
A
A
Be
honest
because,
like
we're
also
doing
that
thing
where
it's
like,
we
got
to
get
feedback
so
ship
it,
and
then
people
will
tell
you
it
didn't
work,
yeah
and
so
in
the
second.
If
we
want
to
be
really
conservative
I
think
like
the
thing
for
release
candidate
is
like
polished,
build
integration
to
build
it
and
something
else
there.
But
like
the
three
builds
things,
maybe
we
should.
D
A
A
B
It's
it's
also
possible
that,
like
maybe
we
just
like
blazed
through
this
faster
than
we
thought-
and
it's
like,
oh
like
we
have
time
to
start
like
laying
the
groundwork
or
MPM
dependencies
or
there's,
obviously
also
the
other
possibility,
which
is
like
Oh
like
oh
sick.
So
is
a
lot
more
work
than
like.
We
thought
it
would
be
and
like
spend
our
time
on
that
yeah
anyway,
it's
fine
anyways.
A
I
think
we
release
candidate
having
like
the
features
that
get
released
in
osek,
so
be
really
good,
usable
and
things
that
we
want
to
shout
from
the
rooftops.
That
would
be
great
okay,
I'm
gonna,
be
with
the
wasm
workshop
at
rust.
Comp
I'm
gonna
be
basically
using
the
stuff
that
is
in
Oh
sick.
So,
with
the
goal
that
I
don't
know,
I
released
I
released
what
some
version
of
was
impact
literally
in
a
tutorial
that
I
taught
it
in
and
I
got
one
so
release.
Another
workshop
seems
about
right,
yeah,.
B
B
C
D
C
And
local
local
NPN
dependencies-
we
don't
have
a
great
story
for
that
by
now,
so
I
would
say
that
maybe
not
a
fully
finished
story,
but
we
should
have
at
least
like
an
accepted
RFC
design
by
the
time
of
the
next
release
candidate,
and
we
should
have
a
much
clearer
vision
of
where
we're
going
in
both
of
these
areas.
I
mean
this
isn't
really
as
in
mind.
In
our
weather
package,
I
mean
it'll,
be
whatever
it
needs
to
be,
but
just
something
around
that
yeah.
A
And,
to
the
extent
that
we
can
clean
up
any
of
the
like
spikes,
we
did
on
that.
One
budget
only
cuz
I
know,
like
Sven,
for
example,
was
like
super
confused
and
thought
that
was
like
supposed
to
be
a
full-fledged
feature
that
worked
and
like
definitely
doesn't
I
think
so.
I
was
like.
Oh
no
did
I
miss
something
yeah.
A
B
A
A
long
freaking
time
ago-
and
there
was
like
an
initial
push
to
annotate
dependencies
and
external
javascript,
using
module
in
the
wesen
binder
and
attribute
in
code,
and
then
we
had
a
bunch
of
conversations
where
people
were
like
I,
really
don't
like
this.
This
is
bad,
we're
like!
Oh,
no
and
then
we
had
a
bunch
of
conversations
like
with
Luke,
talked
to
a
bunch
of
people
and
we
were
like.
D
A
B
But
he
said
that
he
had
a
conflicting
meeting
and
I.
Think
in
my
mind,
like
a
good
goal
for
release
candidate,
for
the
book
would
be
to
integrate
like
the
templates
that
we've
been
building
and
Waze
and
pack
workflow,
which
is
something
we've
been
talking
about
for
a
long
time
and
I.
Think
it's
like
time
that
we
actually
give
it
a
deadline.
So
that
happens
well.
A
Hard
on
getting
the
templates
going,
so
that's.
Why,
like
the
PR
to
pull
hello,
world,
was
impact
out
of
the
book
repo
and
into
the
Westerbeck
repo
has
taken
a
second,
because
I'm
also
basically
audited
the
entire
hello
world
and
replaced
all
of
the
stuff
with
the
template
work
so
taking
a
small
bit
of
time,
but
when
it
lands,
it
like
shouldn't
need
to
be
that
cleaned
up
and
then
from
there
turning
my
attention
to
the
game
of
life.
So
if
anybody
else
wants
to
like
start
on
that,
that
would
be
delightful.
Okay,
so.
B
B
D
B
A
B
B
D
A
D
B
A
B
I
agree
and
and
I
think
like
it
definitely
makes
sense
to
have
like
whichever
one
we
choose
to
have
the
other
one
as
like
an
appendix
kind
of
thing
just
to
like,
like
here's,
how
it
would
work
but
like
I,
really
want
the
the
game
of
life
tutorial
itself
to
be
like
not
necessarily
like
opinionated,
but
not
to
distract
with,
like
all
the
different
options,
because
it's
like
there's
always
another
option.
Another
way
of
doing
something,
and
we
want
to
like
help
people
get
on
like
a
really
good,
fast
path
and
and
so
like.
B
F
So
I
have
some
idea
here,
probably
okay,
since
you
have
said
we
can
take
it
offline,
you
can
take
it
offline
with
just
to
put
out
my
idea
here.
So
it's
based
on
the
website
experience
that
I'm
doing
there.
Basically,
we
are
trying
to
say
people
that
is
interoperable
with
Java
Script,
which
means
you
can
use
it
with
JavaScript.
So
why
can't?
F
We
have
an
example
also
for
try
the
same
thing
like
take
any
JavaScript
library
that
is
available,
pain,
point
to
the
pin
point,
one
area
where
it's
having
low
performance
and
use
that
change
that
with
rust
and
then
use
that
implementation
and
the
new
asset
back
to
publish
it,
which
means
it
also
shows
people
that
you
can
do
this
stuff,
and
it
also
aligns
with
the
vision
or
something
that
we
have
to
the
website.
I.
A
A
A
I
mean
it's
good.
I
actually
have
a
pretty
good
library
where
that
might
work
well,
which
is
the
markdown
parser
for
MPM
marky-mark
down.
It
has
some
native
dependencies
a.k.a
new
guruma
and
people
have
already
taken
a
uma
and-
and
I
compiled
it
to
Azzam
and
liked
the
place,
and
so
I'm
not
saying
that
we
teach
people
to
rewrite
and
make
a
room
ax,
but
I
think
that
there's
maybe
something
we
can
just
like,
find
some
low-key
parts
or
in
JavaScript
we
might
place
a
little
bit
of
it.
Yeah.
B
I
think
this
is
also
a
really
good
thing
for
like
using
as
case
studies
like
if
people
want
to
do
this
kind
of
on
their
own.
Of
course,
with,
like
you
know,
the
cooperation
of
the
maintainer
z--,
who
are
interested
and
not
just
like
you
know,
trying
to
go
in
and
being
like,
hey
we're,
replacing
your
with
rust,
like
that's,
not
a
good
look
but
like
with
cooperation
and
and
then
be
like.
B
You
know,
here's
this
whole
story
and
like
here's
bench,
Marcus
or
whatever,
right
and
like
then
that's
great
material
to
have
for
the
website
and
probably
from
our
book
too
and
point
to
like
here,
are
like
success
stories
of
using
restaurant
Azzam,
yeah
yeah.
It's
just
like
another,
additional
way
that
that
could
be
useful.
Last.
A
F
There
are
people
who
are
doing
as
part
of
google
Summer
of
Code
and
they're,
making
a
progress
in
it,
but
I'm
not
too
sure
whether
it's
completed
or
not.
It's
not
completed
it
and
they're,
making
it
kind
of
like
I've
tried
with
using
with
me
on
changing
certain
parts
of
Awesomeness
or
if
a
pact
with
neon
library,
but
there
was
not
successful
with
that.
If.
F
B
A
Sorry
so
the
one
thing
that
I
was
thinking
of
in
adding
the
book
to
has
impact
is
that
a
couple
of
people
have
mentioned
to
me,
and
this
is
kind
of
I,
don't
know
probably
JavaScript
culture
seeping
in,
but
having
a
little
landing
page
for
the
tools
can
be
really
nice
and
so
because
I'm
already
going
to
be
Otto
deploying
to
gh-pages,
instead
of
just
having
the
landing
page,
be
like
the
first
page
of
the
book,
I
thought
about
maybe
making
like
one
HTML
page.
That's
like
this
is
the
tool.
A
F
A
C
I
think
that
this
makes
sense
in
terms
of
like
there's
not
really
any
skin
off
our
back
it'll
be
probably
be
pretty
simple
and
it's
gonna
be
very
easy
to
link
to
like
more
in-depth
documentation
and
I.
Think
so
like
this
makes
total
sense,
in
fact
I
would
probably
say
not
was
imagined
because
we
don't
actually
want
anyone
to
look
at
that.
A
B
Wonder
if
this
would
be
like
a
good
goal
for
the
final
milestone
for
2018,
because,
like
you
know,
if
we're
gonna
have
like
a
nice
like
landing
website
like,
we
would
definitely
want
it
by
then,
but
I'm
also
sort
of
sort
of
feeling
like
we
have
a
lot
important.
We
have
a
lot
of
stuff
going
on
so
far,
at
least
for
this
release.
Candidate
yeah.
A
I
mean
for
I'm,
not
talking
about
like
doing
it
right
of,
like
my
thought,
was
when
I
push
the
book.
Should
the
book
actually
just
have
an
index.html
that
links
to
the
book
it
has
Ferriss
wearing
the
construction
cap
with,
like
the
words
wise
and
black,
and
a
link
that
says,
read
the
docs
and
nothing
more
like
literally
three
tags.
B
A
A
A
D
A
I
mean
I'm
speaking,
like
kind
of
from
like
my
learning
style,
which
is
like
very
book
of
verse.
Actually,
like
usually
I'm
like
I,
want
to
start
a
project
and
like
I,
do
not
want
to
have
to
read
any
paragraphs
to
know
how
to
start.
So
if
there
was
like
something
that
just
said
use
these
templates
to
get
started,
and
it
was
just
like
a
bulleted
list
where
there
was
like
four
links
or
whatever
my
brain
would
be
really
happy
with
that.
A
I
think
there
I
think
that
a
lot
of
people
will
discover
the
templates
by
eating
the
books
and
the
tutorials
and
I
think
that's
good,
but
I
think
also
like
I
could
imagine
a
world
where
people
are
like
I
want
to
get
started
and
then
like
I
would
just
be
like
look.
We
have
templates
and
just
like,
send
them
away,
maybe
like
oh
great.
D
B
B
A
A
A
A
B
A
B
A
B
The
point
is
like
like
manually
bumping
dependencies
is
like
a
large
part
of
the
maintenance
burden,
I
think
and
especially
for
these
projects
that
are
like
not
actually
really
using
that
much.
It
should
be
pretty
easy
to
like
automatically
keep
them
up
to
date
and
yeah
and
then
see
I.
That's
that's
a
great
point.
Thanks
for
bringing
that
up
anything.
F
A
D
B
E
B
A
Was
just
gonna
say:
there's
like
an
outstanding,
like
would
be
great
if
someone
wanted
to
pick
up
just
for
the
helloworld
less
impact
to
break
right.
Now
we
have
a
section
that
makes
it
you
like.
Has
it
consumed
using
webpack,
but
there's
like
zero
reason
why
we
can't
have
this
equally
similar
chapter?
That's
about
consuming
it
with
parcel.
C
A
B
A
B
A
A
A
B
B
B
A
A
A
Stage
2
so
stage
1
is
you
have
a
draft?
That's
like
reasonable,
like
the
vast
majority
of
the
content?
Is
there,
but
maybe
it's
not
the
best
or
like
not
worded
the
best.
I
think
one
thing
that
I
know
some
deal
has
been
working
on
that
we're
gonna
have
to
probably
spend
a
fair
amount
of
time
doing
in
stage.
2
is
finding
like
case
studies,
user
stories
and
examples,
and
so
Stage
three
is
like
review
with
the
team,
but
I
think
spending
a
little
time
like
either
helping
people
who
are
using
this
technology
right.
A
B
B
C
A
B
Mean
he's
20,
so
we
can.
The
thing
is
it's
not
like
quite
shipping
yet
like
I,
think
it's
part
of
like
this
kind
of
like
beta
and
I.
Don't
know,
but
like
he's
writing
a
blog
post
about
it.
I
think
like
like
a
there's
opportunities
for
like
helping
helping
the
blogpost
be
as
impactful
as
it
can
be
and,
like
you
know,
helping
provide
feedback
and
things
like
that
and
if
you're
interested
in
that,
let
me
know
and
I
can
connect
you
and
then
to
like
it'll
just
be
like
another
good
thing.
B
We
can
point
to
I
think
once
the
blog
posts
are
out
there,
I
think
yeah
I
think
it
doesn't
make
sense
to
point
to
like
a
github
project
and
say:
look
they
used
restaurant
webassembly
but
like
there
needs
to
be
that
kind
of
like
like
digesting
in
in
the
form
of
like
a
blog
post
and,
like
you
know,
kind
of
something
that
tells
a
story.
Yeah.
B
B
A
A
B
Yeah
aside,
I'm,
just
like
so
disappointed
with
github
issues
and
like
milestones
and
everything
it's
like
there's
like
issues
milestones,
projects
like
some
can
be
across
repos.
Some
can't
like
I.
All
we
want
is
to
be
able
to
say
that,
like
one
issue
is
blocked
by
another
issue
and
then
like
I
can
build
milestones
by
just
having
an
issue
that
all
it
is
is
blocked
by
a
ton
of
stuff
like.
Why
is
it
so
difficult,
but
I
digress.
B
B
A
I
think
one
of
the
issues
I
was
running
into
is
like
in
thinking
about
the
2018
rust
edition.
Like
any
time
someone
files
like
a
bug
that
is
true
and
was
impact.
There
is
a
truth
to
it
actually
being
blocking
for
the
rest
2018
edition,
but
then,
when
we
do
check-ins
everyone's
like
there's
20
issues
I'm
like
yeah,
that's
because
there's
like
tiny
bugs
that
we
need
to
fix
that
are
just
labeled
as
that.
So
maybe
I
won't
do
that
anymore.
So
I
don't
know
it's
like
giving
an
honest
representation.
A
B
B
B
F
F
B
A
Yes,
but
I
do
know
that
Lynn
Wentz
the
one
in
Berlin
and
that
there
have
been
pretty
in-depth
conversations
about
webassembly
and
it's
not
it's
not
a
horrible
idea
to
have
some
sort
of
presents
for
every
maybe
could
talk
about
this
there,
because
it's
also
a
good
spot
to
learn
about
the
node
web
assembly.
Integration
work,
yeah,
I,
don't
know
who
would
be
actually
doing
it.
I
don't
even
know
if
I'm
available
Steve
might
want
to
do
it.
Yeah.