►
Description
This is the closing talk for RustCon Asia, talking about updates from the Rust community. You can find the slides here: https://github.com/nrc/talks/blob/master/rustcon-asia-19/words-from-the-core-team.pdf
B
Again,
this
is
a
great
start,
I'm
much
happier
than
last
time.
I'm
gonna
talk
today
on
behalf
of
the
core
team
and
just
say
a
few
words
about
sue,
think
about
where
rust
is
right
now
and
where
we
hope
rust
is
going
to
be
going
over
the
next
year,
but
I
I
just
want
to
start
by
saying
a
few
words
about
the
conference.
B
B
B
B
B
B
These
are
all
kind
of
community
driven,
homegrown
events
and
it's-
and
it's
just
really
great-
that
this
is
this-
is
happening
and
I
and
I
look
forward
for
this
happening
more
and
to
have
for
kind
of
a
a
better
relationship
between
the
various
kind
of
international
Ross
communities.
And,
in
fact,
that's
one
of
the
key
priorities
for
the
community
team.
This
year
is
to
improve
internationalization
and
improve
work
with
the
international
communities,
but
I'm
I'm,
getting
ahead
of
myself
talking
about
2019
I
will
talk
about
20
18
first,
so
20
18
was
a
good
year.
B
We
released
the
2018
Edition,
which
was
very
exciting.
This
is
a
key
part
of
rusts
policy
of
stability
without
stagnation
and
what
that
means
is
we
want
rust
to
keep
improving
to
keep
getting
better,
but
we
don't
want
to
do
that
if
it
means
breaking
your
code
and
the
the
2018
edition
is
an
opportunity
for
us
to
kind
of
future-proof
the
next
few
years
from
the
improvements
and
kind
of
deprecated,
some
of
the
the
stuff
that
probably
shouldn't
have
been
there
in
the
first
place.
B
So
what
was
actually
in
the
2018
edition
I
think
it
was
quite
an
exciting
bunch
of
features
on
the
language
side.
We
we
got
non
lexical
lifetimes,
which
makes
the
Baro
tracker
just
a
little
bit
less
frustrating.
We
added
stable
support
for
a
not
all,
but
a
wide
selection
of
procedural
macros,
which
are
an
extremely
powerful
feature.
B
B
We
shipped
1.0
versions
of
rus
formats
and
Clippy,
which
very
popular
tools
in
the
in
the
rust
ecosystem,
and
we
made
great
progress
on
IDE
support
and
we
ship
the
cargo
fix
tool
that
I
just
talked
about,
without
which
I
think
the
addition
would
have
been
a
much
harder
sell
like
mod,
much
more
friction
in
moving
from
2015
to
2018,
and
we
also
had
some
domain
working
groups
focusing
on
the
domains.
Web
assembly
embedded
computing,
command-line
interfaces
and
networking
and
all
these
domains
make
great
progress
last
year.
B
So
overall,
my
feeling
now
is
the
rust
is
a
working
language.
It's
I
mean
it's
still
a
relatively
new
language,
but
it
doesn't
feel
like
I've,
really
out
there
risky
choice
to
make
if
you're
choosing
a
programming
language,
it's
certainly
not
experimental
anymore.
It's
certainly
not
a
toy
anymore.
It's
it's
a
language,
you
can
get
real
work
done
and
the
2018
survey
backs
that
up.
I
just
want
to
talk
about
a
few
of
the
highlights
in
the
2018
survey.
B
30%
of
those
respondents
use
rust
professionally
at
work
and
again
this
is
tracking
up
year-on-year,
so
we
see
rust
being
taken.
It's
not
just
early
adopters
kind
of
learning
it
in
their
own
time.
It's
you
know.
A
lot
of
people
are
using
it
to
get
work
done
and
25%
to
respondents
working
on
code
bases
which
are
10,000
lines
or
more,
which
is
kind
of
like
a
medium
to
large
a
code
base.
But
this
shows
that,
like
it's,
not
just
toys,
it's
not
just
experiments
or
prototypes
we're
getting
work
done
on
serious
projects.
B
This
is
a
really
interesting
chart
to
me.
This
is
how
long
have
you
been
working
with
rust
and
what's
interesting?
Is
that
about
a
quarter
about
25%?
Respondents
have
been
using
rust
for
two
years
or
more
and
approximately
the
same
about
25%
again,
who
have
been
using
rust
for
less
than
three
months,
and
what
that
shows
to
me
is
that
we
are
still
getting
lots
of
new
users.
Lots
of
people
are
still
coming
to
rust
and
at
the
same
time
lots
of
people
are
still
sticking
around.
B
Think
the
the
the
survey
number
I'm
most
proud
of
is
this
one
is
that
only
two
percent
of
respondents
felt
unwelcome
in
the
rust
community,
and
you
know,
given
what
a
lot
of
internet
communities
are
like.
This
is
a
really
great
results.
I
think
I'm
much
less
proud
that
this
this
number
has
a
lot
of
regional
variation.
So
in
China
the
number
was
8%.
B
My
final
highlight
from
the
from
the
survey
is
93%.
Respondents
have
never
experienced
a
backward
compatibility
issue
and
given
this
core
principle
that
I
mentioned
earlier
stability
without
stagnation,
this
is
a
really
important
part
of
that.
This
is
a
really
big
number
of
people
who
are
getting
the
guarantee
that
we
want
them
to
get
and
the
remaining
7%
nearly
all
of
those
were
very
minor
easy
to
fix
problems.
B
No,
we
we
we've
still
got
a
lot
to
do
and
there's
still
a
lot
of
improvements
we
can
make,
and
so
let's
talk
about
2019
there,
we
recently
accepted
an
RFC
laying
out
the
2019
roadmap
and
there
will
be
a
blog
post
about
that.
Hopefully,
next
week,
the
overall
theme
for
for
2019
is
about
maturity,
and
I
mentioned
earlier.
That
I
feel
like
rust
is
feeling
like
a
warm.
You
know,
mature
language,
where
you
can
get
serious
work
done,
and
we
want
to
take
that
even
further.
B
Ways
in
which
we
can
set
us
up
to
continue
to
grow
and
continue
to
do
so
in
a
in
a
good
way,
rather
than
kind
of
losing
some
of
the
good
things
that
we
have
at
the
moment,
and
a
key
part
of
that
is
about
governance.
How
is
the
project
run?
How
what
are
the
the
leadership
structures
because
of
the
last
three
years
rust
is
grown
in
immensely?
It's
a
it's
got
a
huge
number
of
users
now,
and
we
have
to
make
our
governance
structures
scale
with
the
growth
of
the
community.
B
An
example
of
this
is
the
iris
process.
The
RFC
process
is
great.
It
means
that
we
can
do
all
of
our
design
work
in
the
open.
Nearly
every
decision
that
or
every
significant
decision
which
is
made
in
the
RUS
project,
is
made
via
the
RC
process
and
is
made
in
the
open,
but
we've
gone
through
nearly
13-hundred
RFC's,
since
that
we
we
started
the
process
around
kind
of
1.0
time
just
before
1.0
and
like
we've
well
past
the
point
where
one
person
can
keep
track
of
every
RFC
discussion.
B
In
fact,
we're
pretty
much
part
past
the
point
where
you
can
keep
an
eye
on,
say
all
the
language
axes
or
all
the
library
RFC's,
even
if
you're
working
full-time
on
rust,
which
a
great
number
of
people
in
the
community
aren't,
and
even
if
you
want
to
focus
on
just
like
a
few
prod
rfcs.
Some
of
the
discussions.
You
know,
we've
seen
nearly
seven
hundred
comments.
B
B
B
Here's
a
list
of
some
of
the
things
on
our
mind,
so
custom
allocators.
This
is
a
big
demand
for
people
writing
large
systems,
especially
more
low-level
projects
async/await
for
asynchronous
programming.
I,
probably
don't
say
anything
about
that.
It's
a
it's
a
pretty
well-known
feature
by
now
constant
generics,
generic
associate
type
specialisation.
These
are
all
kind
of
big-ticket
language
items.
They're
all
the
design
is
pretty
much
done
for
all
all
of
these
things.
In
most
cases,
the
implementation
is
pretty
much
done.
B
We
just
need
to
get
some
of
the
wrinkles
out
and
stabilize
it
and
custom
registries
in
cargo
is
another
big-ticket
item
that
we
we
need
to
get
done,
and
the
third
theme
for
the
year
is
polish,
although
by
now
you
know,
the
the
shape
of
rust
is
really
set.
We're
not
gonna
see
any
big
changes
right.
We're
not
gonna
announce
this
year
that
we're
giving
up
on
ownership
and
the
garbage
collection
is
the
way
forward.
But
there
are
like
lots
of
places
where
we
can
polish
some
more
rough
edges
off.
B
B
Okay,
that's
everything
that
I
have
I
I
help
you
of
kind
of
excited
for
what's
gonna
happen
this
year.
I
know
that
I
am
and
I
hope
you
in
are
able
to
attend
some
of
the
workshops
and
enjoy
those,
and
please,
if
any
of
this
stuff
is
interesting,
come
find
me
over
the
next
couple
of
days
and
have
a
chat.
Thank
you
very
much.
B
C
I'm,
a
volunteer
and
I
have
I
have
a
last
technical
question
and
really
quick
as
a
core
team
member.
Can
you
recommend
an
IDE
or
text
editor
for
the
rest
of
the
russ
committee,
because
you
know
the
the
IDE
for
rust
is
not
it's
less
mature
than
the
other
language
like
or
Java.
So
what
should
you
recommend
for
the
rest
of.
B
Us
I
I
would
recommend
using
the
editor.
You
like
I
I,
know
that
if
I
tell
Annie
max
user
to
use
vim
or
vim
user
to
use
Emacs,
it
won't
be
popular.
If,
if
you
like,
a
very
full-featured
IDE,
then
IntelliJ
has
great
support
for
rust.
A
lot
of
the
IntelliJ
features
that
are
available
for
say,
Java
or
Scala,
whatever
you
you
get
for
rust
as
well.
If
you
like,
a
more
lightweight
IDE
vs
code
is
pretty
good,
I
mean
it's
a
fantastic
editor
and
the
rust
support
is
pretty
good.
B
I
am
a
big
fan
of
more
lightweight
editors
like
sublime
text
or
Adam,
both
of
which
have
kind
of
syntax
highlighting
and
can
support
that
they
are
LS.
If
you
like,
having
more
information
like
that
around,
but
really
like
choosing
an
editor
is
such
a
personal
choice
that
I
wouldn't
recommend
one
over
another
I'd
say
more:
stick
to
the
Odyssey
you'd
like
and
the
the
support
will
be
there.
Maybe
not
you
know
as
good
as
you're
used
to
and
Java
or
something
but
there's
there's
stuff
there.
Thank.
B
Deliberately,
no,
it's
because
kind
of
logos
and
trademarks,
and
so
off
it's
so
on.
It
gets
very
boring
and
legal
and
it's
nice
to
have
a
mascot
which
is
not
official
and
with
which
you
can
do
whatever
you
like.
So
if
you
want
to
make
your
own
version
of
Ferris
knock
yourself
out
like
go
ahead,
make
your
own
toy
make
badges
whatever
we
yeah
it's.
It
is
the
russ
community
logo.
D
D
D
A
B
B
It
I
think
it
depends
very
much
who
you're
trying
to
sell
it
to
I
would
say
very
different
things
to
your
CTO
versus
like
another
engineer,
but
kind
of
the
I
mean
the
the
kind
of
like
the
higher-order
bit.
Is
that
if
you
need
performance
and
if
you
need
you
know
low
memory
usage
or
you
can't
tolerate
garbage
collection,
then
rust
will
make
you
much
more
productive
than
other
languages.
By
using
rust,
you'll
have
write
less
bugs.
You
will
spend
less
time
debugging,
and
that
is
a
huge
reward.
Thanks.