►
From YouTube: 30 August 2018 Meeting
Description
The Rust WebAssembly Working Group meeting from 30 August 2018.
A
A
B
A
B
A
The
user-facing
documentation
overhaul
I
added
a
couple
new
things
to
the
checklist
here,
which
was
how
to
do
testing
with
Wasden
Benjen
test,
especially
since
I
have
a
almost
ready
to
land
as
impact
test,
subcommands
yeah
other
than
that.
This
is
still
kind
of
just
mostly
waiting
for
like
web
sis
to
be
published
so
that
we
can
add
documentation
for
that
and
yeah,
and
it's
I
think
other
than
that.
It's
in
a
really
good
place.
A
Totally
understandable
yeah
she
did
like
follow
up
and
ask
like
what
the
issue
which
issue
it
was
again,
but
yeah
I,
just
I,
don't
know
we're.
Pretty
close.
You
know
here.
The
mostly
what's
left
is
just.
We
need
to
actually
implement
webassembly
instance
in
JSS,
and
then
we
can
add
the
extends
and
then
the
others
are
all
kind
of
just
objects
that
are
really
more
like
namespaces
and
it
doesn't
really
matter
that
much
whether
they
have
extends
or
not
so
I.
Don't
know
again
like
this
is
pretty
much
done.
A
D
A
C
D
D
C
A
F
A
G
Wasn't
back
template
the
rust
template
and
I
would
say,
make
it
wasn't
pack
released
as
soon
as
possible,
because
currently
the
template
is
broken
because
it
uses
an
unreleased
user's,
Verizon
pack,
pill
which
is
not
released
yet
so
everyone
who's
trying.
This
right
now
is
actually
running
into
troubles
yeah
so
as
soon
as
possible
would
be
for
UX
for
people
trying
it.
A
H
A
B
E
So
the
thing
with
the
init
command
is
that
it's
quite
slow
for
our
use
case,
because
we
just
want
to
do
the
project
and
they
need
command
is
actually
in
studying,
wasn't
wenjian
in
this
kind
of
stuff.
So
we
cannot
use
it
to
actually
watch
and
rebuild
this
card
life.
That's
why
we
went
with
the
document
so.
A
E
F
E
E
A
So
the
next
issue
here
is
the
publish
the
website
and
there's
a
little
bit
of
movement
on
that.
So
we're
very
close
to
being
done
here.
I
added
a
new
unchecked
checkbox
to
this,
which
is
the
web
ID
all
callbacks,
because
I
don't
think
it
makes
sense
to
publish
web
says
without
being
able
to
add
event
listeners
for
example
and
I
believe
it
was
ADP,
filed
an
issue
about
this
as
well
and
yeah.
A
So
it
just
doesn't
make
sense
to
release
without
that
and
then
the
other
thing
is
Alex
and
I
were
talking
the
other
day
about
web
sis
and
it's
slow
compilation
times,
because
it's
generating
crap
ton
of
rust
or
every
single.
You
know
API
that
exists
on
the
web
and
it
takes
like
you,
know,
20-something
seconds,
to
compile
on
fast
machines
and
do
we
care
about
I
mean.
B
So
Alex
my
opinion
is
yes,
there
should
be
a
blocker
and
my
best
idea
that
I
have
for
making
it
for
the
reasonable
time
frame.
I'm
fixing
this
is
adding
a
per
ton
of
features
to
web
sis
and
basically
say
that
when
you
enable
a
feature
you're,
basically
enabling
that
ideal
file-
and
so
it's
on
you
like,
we
can
provide
some
documentation
for
that.
B
But
it's
on
users,
then
just
say
I
want
face
if
there's
a
tiny,
subset,
mm-hmm
and
over
time,
I
think
like
right
now,
if
you
enable
one-way
audio
file,
it
might
not
be
that
useful,
because
everything
it
depends
on,
isn't
also
enabled,
and
so
we
might
be
able
to
over
time,
draw
graphs
between
these
dependencies
and
say
like
when
you
enable,
like
the
canvas
context
like
you'll,
get
a
bunch
of
other
stuff
that
is
required
for
using
it
at
all.
But
for
now
I
think
it's
a
simple
thing.
B
B
A
B
A
A
Okay,
well,
let's
take
this
discussion
to
the
issue
for
the
future.
Okay,
so
overall
I
think
we're
doing
like
really
well.
We
set
out
like
a
huge
amount
of
stuff
to
do
for
this
cycle
and
I
think
pretty
much.
All
of
it
is
like
super
on
track,
so
congrats
everyone
thanks
for
all
the
progress
we've
been
making.
D
A
Let's
jump
into
the
like
each
sub
goal:
status
updates,
I
feel
like
we
just
went
over
web
sis
I,
don't
think
we
need
to
get
into
that
more
Azzam
back
I
can
do
an
update,
which
is
that
soul,
as
impact
is
now
downloading,
hasn't
been
Jen
when
available.
Instead
of
doing
a
cargo
install
and
of
course
this
is
not
released.
Yet
it's
like
way
faster,
assuming
you
have
a
good
internet
connection,
building
web
engine
from
sources
like
unknown,
like
30
seconds
or
so
a
minute
and
downloading
it.
It's
like
one.
Second,.
A
A
A
A
C
F
A
Yes,
we
need
to
do
that.
I
will
file
an
issue
so
I
know
we
have
an
issue
for
doing
that
in
wesam
pack,
but
it's
not
clear
to
me
that
that's
the
right
place
to
do
that.
I
think
it
probably
wants
it
in
its
own
repo,
so
that
we
can
enable
depend
a
bot
and
like
automatically
stay
up
to
date
with
all
the
things
yeah
I
guess
that
might
not
work
actually
for
the
template
because
it
has
the
like
mustaches
style.
You
know,
placeholders
I,
don't
know
if
depend
a
bot
will
handle
it.
C
C
A
Yeah
so,
basically
like
for
a
long
time,
we've
wanted
to
talk
about
like
kinda,
like
using
the
less
impact
workflow
in
the
game
of
life
oil
and
had
been
kind
of
waiting
on
like
newer,
Wesson
PAC
releases.
That
had
you
know
likewise
impact
build
and
stuff.
But
then,
since
it's
so
easy
to
just
rename
in
it
to
build
once
we
ship
that
I
just
went,
did
it,
and
so
it's
all
integrated
into
the
tutorial.
Now
and
there's
a
new
section
on
publishing
a
rust
generated,
wasm
NPM
package
to
NPM
and
yeah.
A
And
the
other
thing
those
interesting
is
there
was
like
some
bugs
that
came
in
as
part
of
that
like
so,
you
have
to
do.
Npm,
link
after
NPM
install
and
like
people
like
found
that
and
filed
issues,
which
is
great.
That
means
people
are
actually
like
going
through
the
whole
tutorial
and
everything
so
very.
D
A
A
Yeah
debugging
not
much
updates
the
proof
of
concept
that
URIs
been
working
on
is
kind
of
like
making
its
way
upstream
into
the
bugger
HTML
and
other
places.
The
like.
Basically,
it
be,
the
non
Firefox
browsers
are
not
in
a
place
where
they're
ready
to
talk
about
debugging,
yet
which
is
kind
of
like
cool
for
Firefox.
That
they're
like
ahead,
but
like
not
great
for
everyone
else.
A
Uri
is
prototyping
that
as
well
and
he's
writing
that
and
rust
using
the
Gimli
package
for
parsing
dwarf
and
then
that
whole
thing
is
going
to
be
compiled,
tool,
Azzam
and
so
will.
When
we
debug
laz
them
will
be
debugging
wasm
with
wasm
it'll
be
very
fun
and
kind
of
met
a
circular
and
all
of
that
stuff.
A
Yeah
and
then
templates
I
feel,
like
templates,
we
already
kind
of
talked
about
in
both
the
triage
and
other
earlier
sections.
So
unless
anyone
has
anything
else,
they'd
like
to
talk
about
templates
I,
don't
think
there's
much
more
to
say:
okay,
that's
everything
we
have
on
the
agenda.
Does
anyone
have
anything
else
they'd
like
to
bring
up
to
the
group.
B
F
G
D
G
Physically,
where
Hogwarts
wasn't
pack
and
why
you
should
use
present
pack
explaining,
wasn't
fine,
Chen
and
and
then
going
even
into
chases,
and
the
last
lesson
is
going
to
be
like
quick
demo,
a
question
pack,
it's
not
note
ready
yet
so
I,
oh
hey!
You
can
also
run
webassembly
note,
but
yeah.
That's
not
wasn't
pack
yet,
but
once
that's
ready,
I
can
add
a
lesson
later
on
about
how
to
demo
wasn't
a
keen
nose.
Yeah,
that's
a
rough
overview.
Actually
I
can
I
can
post
it
in
the
in
the
paper.