►
From YouTube: 26 July 2018 Meeting
Description
The Rust WebAssembly Working Group meeting from 26 July 2018.
A
B
Alright,
welcome
to
another
meeting
everyone,
hello,
so
RFC,
triage
I,
don't
think
we
have
any
new
RFC's,
but
if
anyone's
interested
I
think
we're
getting
pretty
close
to
entering
FCP
on
the
inheritance
RFC.
So
please,
if
you
care
about
how
inheritance
works
in
like
waves
of
engine
and
the
web's
disk
rate
that
we're
building
go,
take
a
look
at
that
and
drop
your
thoughts
in
the
issue.
B
And
let's
move
on
to
2018
triage,
so
there's
a
link
to
all
of
our
issues
open
here,
and
this
should
represent
everything
we
want
to
land
for
2018
and
yeah
and
specifically
I
think
it'd
be
good
to
focus
on
the
2018
preview
too,
which
is
shipping
August
2nd.
So
that
is
a
week
from
today.
Right
now
we
have
the
publishing
the
J
assist
crate
issues,
the
top
on
my
list
at
least
and
I'm
gonna-
do
that
today,
I
haven't
looked
if
anyone
has
commented
with
any
final
concerns,
but
all
the
things
are
checked
in
there.
C
A
B
D
A
A
We'd
actually
like
to
kind
of
shell
out
shell
out,
but
like
move
responsibility
of
that
over
to
the
template
that
we're
building
so
that
the
steps
you
really
have
our
cargo
generate
template
and
then,
as
impact
build
and
wise
impact,
build,
will
do
all
the
things
so
as
far
as
deprecating
in
it
and
moving
over
to
build
I
have
a
couple
ideas
technically
on
how
to
do
that.
But
those
are
the
primary
things
that
we
want
to
do.
A
The
awesome
thing
about
this
is
almost
all
of
the
code
exists
in
PRS
already
we
have
a
few
more
kind
of
steps
to
get
it
all
the
way
there.
But
we're
gonna
aim
for
the
end
of
next
week
to
Lance
that
and
just
like
looking
forward
Oh
six,
that
oh
we're
gonna
move
the
wasm
opt
plasm,
snipped
and
tamil
configuration
stuff
to
the
release
after
this
user
experience.
A
B
E
A
B
C
B
B
Yeah
I
agree
you're
the
better
but
like
I,
don't
know,
there's
so
like
issue
14
the
integrate
wise
impact
workflow
in
208.
Sorry
wrong,
one!
That's
right,
yeah,
I'm,
sorry,
but
that's
the
template.
I'm
sorry
issue,
26,
integrating
wasm
pack
into
game
of
life
like
I,
feel
like
we
kind
of
want
the
likewise
impact
build
command
to
be
there
before
we
do
it
or
else
we're
gonna
end
up
like
integrating
it
twice.
C
A
One
thing
I
can
say
about
like
the
wanting:
was
impact
build
to
be
there
so
I
know
for
the
game
of
life.
Tutorial
I
think
we
might
want,
like
the
wisdom,
optimism,
sniped
and
configuration
stuff
there,
but
my
plan
for
the
command
is
like
we're,
literally
just
renaming
in
it
to
build
so
I'm.
Just
gonna
leave
them
aliased
for
a
while.
So
even
if
the
tutorial
said
wasn't
packing
it
like
you
could
just
it
will
be
a
one
word
like
fix,
but
if
you
had
it
say,
wasn't
packing
it
right
now.
A
B
A
C
A
The
question
I
I
did
have
about
the
boats,
stuff
and
I've
talked
about
this
with
Nick.
Briefly,
what
do
we
think
about
the
Wesen
pack
tutorial
like
so?
Our
book
is
really
like
two
books:
it's
like
the
game
of
life
thing
and
then
has
a
pack
hello,
world
kind
of
like
stuck
at
the
end.
I
would
really
love
to
see
that
tutorial.
That's
stuck
on
the
end,
get
put
into
the
Wesen
pack
of
repo
and
then
have
our
book
just
really
be
focused
on
using
the
game
of
life.
A
C
A
C
G
Have
a
fairly
stupid
question
so
I
need
to
apologize
in
advance
I'm.
Just
now,
starting
working
on
the
chapter
of
my
webassembly
book
is
far
enough
along
in
JavaScript
integration
to
use,
webpack
and
so
I'm.
Just
I
mean
hearing
some
things
about
it
and
maybe
changing
or
is
there
a
reason
why
I
should
hold
off
on
doing
that?
Oh
no.
A
So
the
only
thing
that
is
officially
changing
is
when
wiesen
PAC
was
originally
conceived.
The
idea
was
kind
of
just
like
prep
your
thing
for
publishing,
but
it
turns
out
we
we
threw
it
into
the
wild
and
everyone
was
like
this
is
a
build
tool
and
has
just
been
using
it
as
a
fill
tool
ever
since,
which
is
totally
fine
the
bit.
The
only
change
that
you
will
see
that
would
be
quote
unquote
breaking
is
that
instead
of
typing
was
impact
in
it.
A
You
can
type
wise
impact
build,
but
I'm
gonna
preserve
the
command
as
an
alias
for
you,
but
really.
The
only
change
that
you
would
potentially
see
is
a
renaming
of
the
command
to
be
a
little
bit
more
honest
about
the
fact
that
it's
doing
its
on
the
fielding,
but
we're
gonna
do
that
like
we're
not
seeing
any
interface
changes,
the
primary
thing
is
we'll
be
adding
just
a
lot
more
features
and
things
that
you
can
configure,
but
just
was
impact
in
it
experience
and
what
you
do
there
that
workflow
isn't
going
to
change
at
all.
A
G
I
guess
the
follow-up
question
is:
are
there
any
samples
that
you
think
might
be
really
compelling
to
show
off
more
than
just
the
JavaScript
integration?
But
in
addition
you
know
some
of
the
stuff
that
wasn't
back
does
and
obviously
I
don't
want
to
put
the
game
of
life
sample.
You
know
in
a
published
book.
G
A
Totally
so
one
of
the
fascinating
things
working
group-
that's
kind
of
like
bumped
into-
is
the
need
for
really
good
examples,
for
why
would
you
want
to
write
something
in
rust
and
compile
them
to
web
assembly?
And
that's
because
it
turns
out
that
the
things
that
web
assembly
is
good
at
is
complicated
things
and
things
that
take
a
really
long
time
and
so
in
trying
to
teach
people
workflows,
also
teaching
them
how
to
write
one
of
those
complicated
things
in
rust.
A
Is
it's
just
really
two
jobs
right,
and
so
we
kind
of
settled
on
the
game
of
life,
because
that's
also
like
a
dice
HelloWorld
exercise
for
a
language,
but
I
know
that
some
of
the
things
that
people
are
working
on
and
if
I
were
to
sit
down
and
write
an
example
that
I
think
would
be
incredibly
compelling.
I'd,
probably
write
a
parser
like.
G
Sounds
like
a
good
project,
I'm
running
into
the
same
issues.
So
my
my
book
is
programming
web
assembly
with
rust
and
I'm
struggling
with.
How
do
I
find
something
lines
complicated
enough
to
make
it
seem
like.
Oh
yeah
I
should
write
a
web
assembly
module
for
this
and
not
so
complicated
that
people
new
to
rust
are
going
to
just
prep
themselves
when
they
see
this
chapter
right.
G
B
Or
like
I,
don't
know
if
you
saw
the
oxidizing
source
Maps
article
on
hacks
mozilla
a
while
back,
but
like
it
purses
these
these
source
maps
which
which
contain
like
you
know
like
mappings
from
you,
know
some
minify
javascript
line
to
a
unmodified
javascript
line
right.
It's
like
debug
info
and
then,
rather
than
returning
the
whole
map
of
like
all
the
different.
You
know,
line
numbers
for
line
numbers.
B
C
I'm
gonna
be
a
tad
busy
finishing
up
my
async
class
for
Ross
comp
in
the
next
few
weeks.
I
might
be
able
to
do
it
at
the
very
least.
I
can
look
at
PRS.
I
will
kind
of
give
you
judgement
by
like
next
week
if
I
can
definitely
take
it.
But
if
someone
wants
to
champion
it
now,
then
I'm
willing
to
do
that.
Otherwise,
I'll
just
spend
a
weekend
and
they're
just
push
it
out.
Well,.
A
A
B
A
C
A
B
B
C
A
One
thing
on
that:
Gutowski,
like
that's
like
a
pretty
big
thing,
that
we're
feeling
a
little
blocked
on
is
there
a
chance
that
she
could
push
up
like
a
work-in-progress
or
like?
Is
there
a
way
we
can
make
the
task
smaller
so
that
she
can
feel
successful
and
that
also
we
are
not
like
it's
kind
of
like
our
critical
documentation
with
a
critical
feature
that
we've
been
waiting
on
for
like
a
month
now.
So
it's
just
kind
of
like
a
bad
situation
that
like
we
need
to
get
it
done.
Yes,.
C
That
was
kind
of
when
I
was
thinking
we're
at
it.
So
yeah
I'll
talk
with
her
see
if
we
can
finish
up
and
work
in
progress,
maybe
like
I
think
she
has
at
least
something
for
chapter
zero,
so
that
that
way
we
can
then
utilize
that
and
then
just
kind
of
move
it
to
the
other
ones,
because
it's
like
multiple
branches,
so
like
just
kind
of
take
that
commit
and
then
change
whatever
needs
to
be
changed
for
each
chapter.
So
there's
still
like
a
start
of
that,
yeah.
A
B
A
B
Updating
that
is
kind
of
a
pain.
It
was
like
the
best
thing
I
could
think
of
for
keeping
everything
in
one
repo
and
having
incremental
you
know,
steps
and
everything
but
like
it
also
means
that,
like
we
can't
use,
depend
a
lot
to
keep
wesen
budget
up
to
date,
which
you
know
is
the
thing
that
we're
updating
most
often
and
and
so
the
idea
was
like
what,
if
we
just
only
have
the
finished
product
product
there
or,
and
we
have
like
chapter
0
and
chapter
1,
etc,
etc,
and
we
just
have
the
final
thing
or.
C
A
C
B
Essentially,
yeah
I
kind
of
think
the
template
is
a
bit
of
an
orthogonal
issue
like
like
I,
think
we
just
want
to
maintain
one
master
branch,
that
is
the
final
product
of
the
game
of
life
tutorial
and
then
whether
the
game
of
life
tutorial
has
been.
You
know,
edited
to
use,
be
what
to
work
on
top
of
the
template
or
not
is
a
separate
issue
from.
A
C
The
book
to
show
that
and
then
just
kind
of
coordinate
the
to
be
merged
at
the
same
time.
I
think
that's
fairly
easy
doing
that
and
then
and
then
that
will
then
a
class
I
was
on
a
smaller
chunk
to
just
update
the
one
final
version
to
just
have
that,
which
I
think
would
help
her
out
a
bit
so
that
we
wouldn't
get
that
done
sooner.
Yeah.
B
B
F
A
Mean
if
it
would
also
benefit
cargo
generate
to
have
some
examples
of
people
using
it,
because
hilariously,
the
large
popular
opinion
of
cargo
generate
right
now
is
that
no
one
thinks
it's
useful
at
all.
Oh
thanks
reddit,
but
yeah.
If
we
could
get
that
in
there,
it
would
definitely
help
explain
what
assuming
we
can
separate
that
out.
If
adding
using
cargo
generate
and
the
template
is
something
like
I've
been
wanting
saved,
a
blog
post
or
an
example.
B
A
B
A
H
H
H
Sure,
okay,
so
I
initially
started
with
some
design,
but
that
was
like
it's
not
kosher
and
then
I
updated.
The
design
I
think
I
shared
the
design
with
Ashley
and
Nick,
told
me
and
I
just
raised
through.
That
was
for
that
the
content
might
be
changing
some
something
we
can
add
the
content
of
it
more
crisp.
But
apart
from
that,
I
think
the
sign.
H
For
me
it
looks
good,
but
if
you
guys
want
to
change
it
or
if
there
is
something
that
can
it
has
to
be
updated,
we
can
update
it
there,
but
you
can
go
ahead.
I
will
share
that
screenshot
I,
don't
know
where
to
share
the
screenshot,
probably
so
I
just
shared
with
Nick,
but
for
others.
You
guys
want
to
have
that
screenshot
probably
bring
me
in
this
code.
I'll
just
update
you,
the
screenshot.
Yes,.
A
So
the
one
thing
I
was
gonna
say
is
so
what
it
currently
does
is
it
kind
of?
Does
the
sales
pitch
of
like
why
wisdom
at
all,
and
then
it
kind
of
showcases
our
tools
and
one
of
the
other
things
that
the
working
groups
are
doing?
That
I
think
is
a
really
powerful
thing
that
you
can
add
to
the
site
is
like
real
life.
A
Examples
like
this
in
the
world
and
so
I
know
we
have
this
sort
snaps
thing,
but
there's
been
like
random
content
like
I've
seen
on
Twitter
people
being
like
I,
think
fastly
is
I,
don't
know
if
you
think
Russ
generated
webassembly
or
not
anyways,
it
would
be
really
great
if
we
could,
maybe
maybe
we
should
file
an
issue
on
the
the
Russ.
Wasn't
team
repo
but
collecting
like
real
world
examples
of
people
doing
this
it's
kind
of
like
a
Content
hole
in
that
we
have
right
now
on
the
web
page
yeah.
H
I
think,
like
there's
one
thing
from
Dropbox,
they
were
like
doing
demands
for
this
with
a
person,
be
the
thrust
and
all
those
stuff
but
I'm,
not
particularly
sure
whether
we
have
to
focus
something
that
uses
fashion
by
engine
tooling
and
things
like,
or
we
have
to
just
focus
on
rust
and
webassembly.
Just
that
stuff
yeah.
H
A
H
G
A
B
B
It
is
going
pretty
well,
there's
been
some
work
or
some
some
incoming
work
on
namespaces,
so
we
can
support
like
the
console
and
then
I
believe
we
had
to
disable
some
functionality
that
ended
up,
triggering
like
multiple
constructors
or
something
and
and
caused
some
breakage
I
have
been
a
little
bit
less.
On
top
of
that,
but
I
guess.
The
other
thing
is
that
what
kind
of
the
the
partner
of
the
Webster's
crate
is
the
jss
crate,
which
we
mentioned
we're
shipping
today.
A
I
Don't
think
there's
much
known
as
blockers
no
I
mean
just
we
could
probably
maybe
use
a
renewed
call
to
action
to
kind
of
see
what's
going
on
there,
though
I
think
like
the
namespaces
and
iterables
are
flocking
to
too
much,
and
so
it
might
be.
It
might
be
right
bit
this
point
to
kind
of
have
another
community
jolt
to
try
and
push
people
towards
again.
Okay,.
B
A
Like
I
gave
a
really
comprehensive
was
impacted,
update
what
I'm
not
talking
to
you,
sorry
I'm.
So
sorry,
people
in
my
household
earthing,
I'm
speaking
to
them,
know
so
I
think
what
I
kind
of
set
up
I
mean
I,
guess
I
can
share
a
little
bit
about
the
long-term
version
of
Wes
impact.
So
again,
uux
improvements,
four
five
and
we
want
to
land
five
at
the
end
of
next
week.
Then
six
is
all
the
tooling
and
configuration
support
and
the
goal
for
that
is
mid-august.
A
So,
especially
because
a
lot
of
the
PRS
are
already
there.
It's
gonna
be
a
pretty
quick
turnaround
from
5
to
6
and
then
currently
on
the
roadmap
and
we'll
see
how
this
actually
goes.
But
alex
has
been
working
on
some
really
interesting
testing
stuff
and
maybe
putting
like
a
naive
version
of
that
as
like
a
version
of
Wes
impact
tests.
To
try
and
have
people
play
around
with
is
something
that
I
think
we're
looking
at
four
seven
one
thing
that
I
have
just
not
touch
at
all
yet
and
fascinatingly
has
super
come
up.
A
C
H
H
H
F
B
Okay,
so
whether
or
not
it's
a
good
point
or
a
good
idea,
I,
don't
know
I
thought
having
the
example
would
be
good,
but
again,
if
they,
if
the
target
audience
is
like
CTOs
and
like
maybe
the
code,
snippet
makes
less
sense.
If
the
target
audience
is
like
developers
who
are
interested
in
doing
cool
stuff,
that
I
think
it
does
make
sense
but
like
if
we
do
want
a
code.
Snippet
then
I
think
webassembly
studio
is
the
way
to
go.
A
B
H
Date,
I
have
an
opinion
here.
That's
Instagram,
burying
this
film's
assembly
studio
inside
the
browser
that
we
have
rather
than
I
just
have
the
main
primary
button
which
you
saw
in
that
website.
This
just
goes
there,
so
it
just
goes
to
a
person
a
studio.
So
probably
we
can
do
something
like
that.
If
the
seekers
are
really
interested
to
go
there
and
check
it
out,
they
can
check
it
out
from
there.
The
other
idea
that
I
also
had
was
like
we
can
have
this
tab
determine
three
tabs.
H
The
first
one
is
like
the
rest
core
and
then
the
converter,
vast
and
then
other
Final
Solution
is
like
of
the
citroen
or
in
JavaScript.
How
do
you
call
it
so
all
this
in
the
three
tabs,
but
that
again
kind
of
like
if
you
have
all
for
more
complex
examples,
your
vast
code
is
huge,
so
you
cannot
put
that
inside
so
which
also
doesn't
make
any
sense.
So
that's
the
main
reason
why
I
remove
the
tab.
Editor
editor,
which
were
we
talking
about,
but
yeah.
That's
the
basic
reason
why
I
remove
it?
Yes,.
A
A
There's
also
a
sense
that,
like
the
website,
especially
primarily
a
marketing
site,
it's
gonna
be
mobile,
friendly
and
so
embedding
a
text
editor
in
a
site
in
like
a
small
panel,
but
then
is
gonna
become
even
smaller
on
a
phone
just
might
not
make
sense
at
all
because
it
might
not
be
even
functional.
So,
like
I
have
no
idea
what
webassembly
studio
looks
like
on
a
phone,
but
my
guess
is
not
great
yeah.
C
B
A
For
what
it's
worth
like
so
I
created
the
wesen
pack
template
because
I
needed
something
to
test
cargo
generate
with
and
I
wanted.
Something
like
really
simple,
I'm
still
a
little
confused
about
exactly
what
the
current
state
of
the
template
is
trying
to
accomplish,
because
it
does
feel
like
it
has
both
library
stuff
and
like
put
it
in
your
HTML
stuff
and
I
I,
don't
want
to
go
in
and
like
clear
out
a
whole
bunch
of
stuff
that
I,
don't
think,
makes
any
sense.
A
F
A
B
Okay,
so
yeah
so
I
think
like
whether
it's
split
the
rust
plasm
template
into
just
more
of
a
like
a
library
template
and
integrating
with
the
Weizmann
pack
template
or
turning
the
Russell
Asma
template
into
an
NPM
template
like
it
seems
to
me
like,
like
we
need
one,
that's
like
the
library
and
then
one
that's
like
using
the
library
and
like
creating
the
webpage
right,
yeah
and
and
then
we
want
to
integrate
both
of
those
back
into
the
book.
Yeah.
B
B
B
A
I
I
I
So
the
idea
is
I
wanted
to
make
that
much
nicer
horizon
bunch
in
itself
and
it
has
morphed
into
what
I'm
hoping
is
kind
of
a
what
might
become
an
eventual
nice
testing
framework
for
just
Wiseman
dress
code
in
general,
where
the
idea
is
that
currently,
when
you
write
tests
in
rust
today,
you
just
kind
of
write
some
integration
tests.
You
haven't
really
through
a
file
and
test
/foo
to
Aris,
and
then
you
put
some
pound
test
annotations.
I
You
might
sprinkle
that
in
your
notebook
as
well,
but
then
the
ideas,
though,
we'll
take
that
and
instead
of
writing
contest,
you
write
pound
wise
and
by
Jen
test,
and
that's
it
other
than
that
cargo
test
target
wasn't
32
will
just
work.
That'll
run
tests
in
either
node
it'll
run
it
in
a
browser
where
you
can
like
actually
load
it
up
and
go
hit.
I
The
webpage,
the
bug,
stuff
or
I'll,
run
it
in
the
headless
browser
or
it'll
just
print
out
everything
that
happens
in
a
headless
mode
suitable
for
CI,
but
actually
running
tests
like
in
Firefox
or
Chrome,
on
CI,
on
Travis
or
on
that
air,
whatever
you
and
whatever
so
currently,
this
is
all
implemented
and
actually
sent
as
a
pull
request
to
the
web
by
June
or
posit
or
II.
It's
not
a
super
usable
state
right
now,
it's
still
kind
of
like
wonky.
I
As
is
but
yeah,
that's
kind
of
like
the
current
status
of
that
and
like
eventually,
we
want
to
see
this,
maybe
integrated
into
a
wise
impact
test
command
and
that's
kind
of
like
we
still
want
to
figure
out
some
more
of
the
design
of
how
this
actually
works
internally
and
make
sure
more
people
understand
it
than
just
me,
and
so
I
suspect
it's
gonna
be
tweaked
a
little
bit
over
time
to
actually
get
into
wise
impact.
But
that's
kind
of
the
eventual
end
goals
at
one
point
in
the
future.
I
B
A
Recently,
Nick
and
I
met
with
folks
from
the
parcel
team
and
so
ostensibly
the
way
Wes
impact
currently
works.
It
should
work
out
the
box
of
parcel
and
that's
what
they
told
me.
So
it
would
be
really
awesome
if,
in
just
the
helloworld
tutorial
for
was
impact,
we
have
a
chapter
on
web
pack
and
then,
if
we
added
a
chapter
on
parcel
I
like
to
see
that
actually
work
and
then
just
make
sure
that
that's
good
so
that
we
have
time
if
it
doesn't
work
to
give
feedback
to
the
team
to
be
like
hey.
A
A
They
in
the
meeting
expressed
some
reasons
why
they
felt
some
people
would
still
want
that
and
that's
fine
I
kind
of
think,
a
long-term
that
people
probably
won't
want
that.
You
don't
want
to
have
to
like
implement
every
source
languages
compiler
into
your
bundler.
That's
gonna
be
a
huge
pain
in
the
butt,
but
for
now
like
that's
fine,
but
if
somebody
wants
to
try
and
tackle
on
basically
reproducing
the
section
of
like
integrating
your
new
Azzam
package,
but
do
an
impartial
instead
of
webpack.
That
would
be
awesome.
I'm
very
appreciated
otherwise.
I'll
just
some
day.