►
From YouTube: 20019-02-14 Rust and WebAssembly Working Group Meeting
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
Hey
welcome
to
another
arrest
in
webassembly
work,
your
meeting
yeah.
So
as
I
mentioned
earlier,
I
forgot
to
file
the
issue
about
the
meeting
so
kind
of
small
roster
today,
but
hop
into
it.
So
there
are
no
new
RFC's,
but
we
are
kind
of
getting
closer
to
our
self-imposed
deadline
for
the
2019
roadmap
RFC,
so
I'm,
probably
gonna,
there's
there's
one
less
edit
I'd
like
to
make
to
it
and
then
I
think
I'll
probably
call
for
a
final
comment
period.
A
So
the
big
news
is
that
Alex
ported,
the
kind
of
all
of
our
Wiseman
transformations
and
intrinsic
rewriting
and
everything
to
walrus,
which
is
a
crate
that
is
designed
for
walk,
Bassem,
TASM
transformations,
and
the
idea
is
that
it
doesn't
yet,
but
it
will
eventually
preserve
debug
info,
which
will
help
our
as
a
story.
Obviously,.
B
A
A
B
C
B
A
B
What
I'm
gonna
do
is
add
a
flag
to
wet
sump
engine
to
disable
the
producer
section,
and
then
we
try
and
figure
out
how
to
get
that
under
wasn't
back
as
well.
I
think
it's
a
fiber
one
anyway,
because
people
wanted
like
we
already
have
a
flight
to
turn
off
the
name
section,
and
so,
if
we
can
figure
out
how
to
get,
if
you
can
figure
out
how
to
invoke
that
that'll
fix
the
that'll
fix
the
bug
for
now.
A
B
I
guess
so,
if
it
it's
kind
of
unclear
to
me
when
the
web
pack
bug
came
out
like
I'm,
not
sure
if
there
was
an
update,
which
is
totally
broken
with
the
producer
section
or
if
it's
because
we
change
producer
sections
that
it's
causing
issues,
but
actually
what
I'm
thinking
of
doing
is,
we
should
probably
just
publish
a
release.
It
wasn't
by
Jim
that
by
default
deletes
the
producer
section
and
then,
as
soon
as
this
is
published
at
NPM,
and
then
we
can
suite,
we
can
switch
that
default
back
to
producing
publishing
it
by
default.
B
Actually
had
a
couple
of
small
peers
here
and
there
we
had
so
there
was
one.
C
B
B
Some
broken
web
IDL.
Well,
we
aggressively
deleted
some
web
idea,
but
I
ended
up
actually
needed
to
keep
it
because
it
was
just
miss
annotated.
There's
also,
there
was
a
mild
optimisation
added
for
reflects
where,
if
you're
getting
an
integer
integer
indices,
you
don't
have
to
round-trip
there,
which
is
value,
and
so
it's
a
little
bit
less
efficient.
B
There,
oh
and
then
Nick
you
landed
the
thing
which
is
pythons,
simple,
HTTP
server
will
annoyingly
not
set
the
mime
type
for
wisdom
files,
which
means
that
you
can't
use
it
with
instantiate
streaming
and
so
Nick
isn't
Atlanta
to
fix
and
wasn't
bind
gen
to
say.
Well,
even
if
you
instantiate
streaming
exists,
if
it
doesn't
work,
we're
gonna
fall
back
to
instantiate,
so
it'll
still
work.
Pretty
nice
warning
on
the
console,
saying
like
hey
your
servers
and
do
the
right
thing,
and
so
that
should
get
some
nice
demos
like
any
initial
usage.
A
D
C
D
A
B
A
A
C
A
A
C
I
did
I
did
had
a
look
into
it
and
probably,
if
you
guys
a
half
time
to
discuss
this,
we
can
also
discuss
the
generator
app
that
I
was
talking
about
and
there
was
a
Vashem
app
generator
I.
Think
it's
included
in
the
this
weekend.
Rest
this
this
edition,
so
probably
you
guys
can
give
it
a
try
and
it's
not
updated.
I
just
went
for
a
vacation
and
came
back
so
it's
not
updated.
It's
not
up
to
the
latest
build,
but
I
hope.
I
can
also
move
this
thing
inside
Ross
class
and
repo.
C
A
A
A
Yeah,
so
for
the
folks
who
were
not
at
the
rust
all-hands
in
Berlin,
Ashley,
myself,
Alex
and
Yosh
were
there
and
we
talked
about
a
few
things.
The
notes
are
linked
from
the
this
week
in
rust
and
webassembly
posts.
The
one
app
yesterday,
but
we
talked
about
trying
to
plan
for
1.0
of
awesome
pack
and
kind
of
would
like
feature
wise.
What
do
we
want
to
include
in
the
1.0
which
be
a
surprise
for
anyone?
It's
pretty
much
what's
laid
out
in
the
roadmap
and
then
the
other
thing
we
talked
about
was
like.
A
You
can't
have
this
long-standing
issue
of
like
piping.
The
files
doesn't
work
super
well
and
like
output
on
non
fully
featured
terminals.
Doesn't
work
super
well
and
just
like
kind
of
like
even
deciding
whether
to
print
something
or
not
was
like.
You
know,
we
kind
of
have
been
kicking
that
a
can
down
the
road,
and
so
we
we
kind
of
sat
down
and
came
up
with
plan
for
just
like
a
general
philosophy
of
like
what
the
interaction
with
resin
resin
pack
should
look
like
when
things
should
be
printed
or
not.
A
All
of
these
sorts
of
things.
So
definitely,
look
over
that
I
think
we
ended
up
coming
to
agreement
on
something
that
is
pretty
nice.
What
else
we
talked
about
talked
about
multi-threading
how
to
turn
our
experimental
multi-threading
support
into
something
we
can.
You
know
use
as
a
foundation
for
the
whole
ecosystem
into
like
a
real
library.
Instead
of
a
you,
know,
kind
of
a
an
experiment,
and
also
we
talked
with
Josh
stone
from
the
Rhian
team
about
how
to
get
rayon
working
on
top
of
this
and
the
plan.
A
There
is
basically
there's
some
complications
with
the
main
thread:
read
Alex's
posts.
If
you
want
to
learn
more
about
those
complications,
but
basically
you
won't
be
able
to
just
do
like
you
know,
Rio
and
pair
it
err
like
pair
for
each
or
whatever
and
you'll
have
to
kind
of
submit
that
work
to
the
off
main
thread,
rayon
worker
pool
and
then
kind
of
get
the
result
as
a
future,
because
the
main
thread
can't
block
is
the
thing
here,
but
it
should
be
able.
We.
A
Work
really
well
what
else
we
talk
about?
Oh,
it's!
A
about
car
go
build
hooks.
So,
like
you
know,
super
long-term,
like
you
know,
out
past,
wasn't
back
one
point
out.
We
would
like
building
a
lesson
library
to
be
the
exact
same
as
building
a
rust
library
where
you
literally
just
type
cargo,
build
and
that's
it
and
of
course
the
reason
we
have
lazon
pack
is
because
we
do
all
this
extra
stuff.
A
B
A
A
A
To
the
extent
at
which
the
toolkit
will
encompass
those
opinionated
things,
I
think
we
want
to
focus
more
on
just
having
traits
and
interfaces
that
you
can
use
to
plug
different
ones
in
and
not
so
much
on
like
trying
to
bless
a
particular.
You
know
like
this
is
the
virtual
Dom
library
or
something
right
rather
have
a
garden
that
blossoms
many
flowers,
yeah.
D
So
something
that
comes
to
mind
that
I
wanted
to
talk
to
you.
Real
quick
is
in
the
embedded
space
or
hey
I.
Think
his
last
name
is
mauricio
I,
don't
remember
what
his
last
name
is,
but
they
have
a
similar
setup
with
the
embedded.
How
system,
where
you
have
device
crates,
and
then
you
have
the
hardware.
Abstraction
layer
creates
and
actually
just
a
single
hardware
abstraction
layer
create,
essentially
that
provides
traits
and
then,
when
you,
the
specific
pal
crepe
or
you
know,
device
X,
Y
or
Z,
you
essentially
just
implement
those
traits.
D
So
that's
a
really
great
idea,
because
I
mean
obviously
we've
been
using
Titus
an
example,
but
that's
another
example
of
kind
of
a
pattern.
That's
RTI
played
there.
So
I'm,
not
sure
if
you
guys
have
seen
that
at
all.
But
it
came
to
mind
when
you
were
saying
that
so
figure
that
would
toss
it
out.
There
I
think.
A
A
So
yeah
like-
and
none
of
this
is
like
you
know,
set
in
stone
or
like
already
designed
or
anything,
but
this
is
kind
of
just
like
trying
to
get
to
a
place
where
you
know.
Probably
the
next
step
will
be
trying
to
merge
the
RFC
Road
map
and
then
once
we've
agreed
on
agreed-upon
that,
like
creating
a
space
where
we
can
all
come
together
to
do
the
design
and
the
discussion
and
kind
of
figure
things
out
together.