►
From YouTube: .NET Core Design Reviews: Backlog review
Description
00:00:00 - Approved: Missing several valuable members of System.Console in contract https://github.com/dotnet/corefx/issues/4636#issuecomment-162039060
00:10:27 - Approved: Add ValueTask to corefx https://github.com/dotnet/corefx/issues/4708#issuecomment-162042013
A
B
C
B
I
think
the
new
api's
are
nice.
I
still
have
trouble
with
the
notion
of
introducing
a
new
set
of
API
is
even
though
you
know,
the
current
ones
aren't
great.
They
support
the
same
scenarios
and
so
I
I
struggle
with
the
idea
of
introducing
new
ones.
I,
don't
completely
understand
the
whole
standard,
plat
versus
standard
lib,
vs
court
effects,
distinction,
and
so
I
I,
don't
quite
know
what
to
make
of
it.
But
I,
like
the
mean
in
nothing
with
you,
know
all
other
issues
aside.
The
new
shape
looks
nice.
A
Yeah
I
think
that's
something
we
need
to
talk
about
in
general.
Is
that
what
we
do
with
our
competitor,
because
the
thing
in
general,
like
I,
think
we
said
it
before?
If
you
need
to
think
about
how
we
can
evolve,
don't
make
war
without
moving
the
elephant
every
single
time.
You
add
something,
but
at
the
same
time
there's
a
lot
of
contention
about
what
it
means.
A
There's
a
combat
effort.
Hopefully,
I
can
publish
something
today:
special
threats.
What
we
saw
the
threads
on
home
github
regarding
our
ATO
done
it
interfaces
and
I
think
we
need
to
put
a
bit
stronger.
Put
it
up.
A
All
right,
so
here's
what
I
projected
can
you
share
this?
Can
you
see
the
screen
Stephen
yeah
I
can
take
the
land
that
works
can
find
my
cursor
here.
It
is
awesome,
so.
B
So
scroll
to
the
bottom
rock
there
you
go
right
there:
okay,
so
it's
pallabi
there.
A
B
That's
fine,
so
I
there
may
be
more
stuff
on
console
that
we
want
to
bring
back,
but
these
were
the
ones
that
jumped
out
at
me
and
that
I
saw
being
used
in
a
variety
of
places,
including
there
was
a
whole
discussion
around.
You
know
implementing
something
like
more
advanced
cursor
manipulation
as
part
of
doing
standard.
Read
line
stuff.
You
know
you
want
to
read
a
line
of
text
and
have
a
history
and
be
able
to
go
back
and
forth
and
things
you've
already
typed
and
whatnot.
B
B
A
I
think
and
I
talked
to
Wes
about
console
I,
don't
know
100
*
day
at
this
point,
I
think
the
general
consensus
that
we
all
agreed
proved
is
that
we
should
check
the
holistic
local
console
pretty
much
at
everything
except
for
the
ones.
We
don't
want
to
add
specifically
because
right
now
its
basis
is
the
one
of
all
I
went
into
this
guy
eat,
so
they
be
either.
Add
this
one
right,
I
great.
B
C
A
A
That
we
have
I
think
that's
the
only
the
one
you
want
is
there's
a
this
one,
specific
API
that
that's
essentially
a
copy
of
the
buffer,
where
you
can
say
take
this
thing
over
here
and
copy
it
here.
I
would
like
to
do
pray,
for
example,
scrolling
without
having
to
in
water
screen,
okay,
but
I'll
call
AP,
I
suggest
you
said
foreground
and
background
images
right.
Oh.
B
C
B
C
C
A
C
A
B
A
Mr.
priorities,
here
all
right,
so
I
think
you
for
my
point
of
view.
There's
nothing
wrong
with
adding
those
I
think
the
only
thing
I
would
do
at
this
point
is
like,
if
you
already
looked
at
the
consulate
guys,
which
ones
did
you
not
include,
because
the
thing
it
would
be
good
to
see
is
all
of
console
which
are
the
ones
we
have
netted
yet
and
having
not
done
it
yet,
because
we
didn't
run
in
the
app.
So
do
we
not
add
those,
because
we
think
that
the
wrong
API
is
to
add
Italy.
B
This
sucks
I
think
that
makes
the
pencil.
Let's
say
we
we
could
go,
give
the
thumbs
up
for
all
of
these,
except
for
buffer
buffer
with
buffer
height,
because
those
two
are
tied
in
with
some
the
other
AP
ice
and
then
all
in
addition
to
giving
the
go-ahead
on
those
I'll,
add
the
remaining
list
and
whether
I
think
we
should
add
or
not,
and
why.
Okay.
A
B
A
We
should
let
it
get
around
and
you
read
all
the
next
behavior.
C
B
Okay,
so
this
one
we
meet
you,
the
three
of
us
have
had
email
conversations
about
this
for
a
while
and
so
I
implemented
it
I
have
a
I
didn't
put
up
a
PR
to
follow
the
PAP
I
process,
but
I
have
it
up
in
a
commit
and
I'd
like
to
basically
add
a
new
library,
decor
effect,
so
that
we
don't
have
to
put
this.
You
know
into
desktop
and
whatnot.
It
can
just
be
a
separate
thing
that
sits
on
top
of
it
available
everywhere.
B
We
want
imagining
that
in
the
future,
if
we
were
to,
for
example,
add
a
new
like
a
sink
reader
writer
lock,
maybe
you
could
go
in
there
as
well
and
but
right
now
it
would
basically
just
be
the
value
task
type
and
the
associated
a
waiter
for
it,
and
then,
if,
if
there's
a
proposal
for
Rosalind
to
be
able
to
have
other
things
in
the
return
type
position
of
a
sink
methods,
of
which
this
would
be
one,
and
so
we
would
also
add
the
necessary
builder
types
to
that
assembly.
A
C
Kind
of,
like
you
know
recently,
we've
had
more
discussions
about
this
here.
It's
right,
I
really
don't
like
how
is
kind
of
twist
the
architecture
in
this
factoring
of
our
types
and
libraries.
Because
of
the
you
know,
not
that
framework,
tesco
issue,
I
kind
of
I,
almost
think
that
you
should
consider
doing
function,
facade
and
basically,
that
home
have.
A
B
Variaty,
so
it's
very
helpful
in
the
case
where
you
have
a
very
hot
method
that
usually
complete
synchronously
completes
asynchronously
every
once
in
a
while.
That's
returning
sort
of
arbitrary
values.
So
it's
not
easy
to
predict
the
value
in
those
cash
them
and
in
those
cases
it
can
make
an
absolute
huge
savings.
B
So
it's
sort
of
a
niche
thing
that
doesn't
impact
most
cases,
but
in
the
few
cases
that
it
does
it's
huge
so
like,
for
example,
we
use
this
in
one
place
in
court
effects
now
where
it
had
a
gigantic
impact
in
the
xml
library
for
the
async
aps,
but
that's
the
only
place
we
use
it.
I
use
it
one
place
in
the
channels,
library,
although
that
place,
that
I
use
it
is
public
and
there
were
two
alternatives:
either
a
much
more
expensive
implementation
or
a
much
more
convoluted
api.
C
So
you
see
like
some
times
in
the
past.
We
avoided
experience
because
of
the
cost
of
the
class
task.
Like
you
know,
binary,
reader
and
writer,
you
don't
want
to
read
a
bite,
they
say
v,
you
know
asynchronously.
Yes,
do
you
think
that
the
volume
tasks
improve
the
situation,
not
such
that
you
can
actually
come
in?
You
know
a
single
relations
or
something
like
a
binary
reader.
B
A
What's
the
cost
the
case?
Because
if
you
basically,
if
let's
say
you,
you
have
the
binary
reader
right,
you
already
have
the
buffer,
so
you
just
return
the
bite
from
the
buffer.
So
you
find
the
position
in
the
buffer.
Then
you
return
the
value
task
where
that
by
to
that
position,
what
what
is
it
I
mean?
You
just
had
a
very
thin
structure
at
that
point
right,
but.
B
A
You
know
you
do
a
task
or,
as
you
do
it
synchronously,
then
the
Delta
may
be
huge.
But
if
you
do
the
task
or
survey
to
task
and
the
Delta
between
the
video
task
and
the
tasks
may
be
much
much
bigger
than
the
difference
between
synchronous
and
video
task
right,
so
they
may
still
move
it
into
a
realm
where
it's
at
least
from
an
API
for
doing.
B
B
B
I,
don't
I
don't
have
a
strong
opinion.
I
I,
like
the
prefix,
better
I,
understand
the
argument
that
making
it
a
suffix
allows
it
to
show
up
better
in
you
know
intellisense
and
things
like
that,
although
if
you
type
task
and
intellisense
it's
going
to
narrow
it
down
to
the
set
of
things
regardless
of
whether
it's
a
prefix
or
suffix,
so.
A
I
mean
it's
mostly
sorting,
but
I
mean
given
that
these
things
usually
I
mean
these
are
types
right
I
mean
like
for
most
cases.
I
would
be
more
worried
about
because
these
are
kind
of
tasks
that
you
don't
did
so
not
api's.
You
use
a
lot
yourself
there
they're
created
on
your
behalf
right
so
you're,
not
instantiating
tasks,
necessarily
that
much
so
we'll
be
more
concerned
about
how
it
affect
signature,
sorting
and
stuff
like
that,
but
that
to
me
it
seems
more
like,
like
itself
all
gonna
like
whether
it's
prefix
or
suffix,
both
work
yeah.
A
Mean
arguably
like
for
I,
think
for
task
I
think
we
can
all
agree
that
this
is
not
a
an
API.
You
should
use
a
lot.
It
should
be
used
very
sparingly
in
cases
where
you
know
you
want
that.
My
hunches.
That's
probably
true,
for
all
of
these
cases,
where
we
have
struck
based
alternatives
right
like
video
topic
for
exam,
what
we
think
this
is
used
by
default
or
what
we
say
well,
it
kind
of
depends
well.
A
W
would
say
you
would
rather
have
it
show
up
next
to
it,
because
you
kind
of
want
people
to
steer
it
to
that.
Well,
that
makes
it
I
don't
know
right
now.
Should
we
want
them
to
show
up
side-by-side
or
not?
I
don't
know,
I
think
we
should
just
pick
one
pattern
and
stick
to
it
rather
than
have
two
different
ways
doing.
B
I
agree
we
should
we
have
one
convention,
my
slight
preference
and
again
it's
not
strong.
My
slight
preference
is
for
the
prefix
simply
because
it's
how
like
I
read
the
c-sharp,
you
know
I
read,
see
sharpens
it's
a
struct
foo
or
a
class
foo.
This
is
a
value
foo
versus
a
task
value.
I.
Think
the
value
is
being
like
the
T.
The
generic
t
result
it's
a
task
of
int,
it's
a
task
of
value,
but
that's
a
minor
thing
and
it's
just
my
mental
model.
C
B
C
No
because
if
you
don't
follow
you,
you
may
first
time
value,
activator
and
value.
You
know,
like
intelligence
will,
show
you
many
times.
None
of
them
are
related
tasks.
They
are
just
about
Persians
of
some
other
us.
It's
not
right
has
happened
to
be
a
you
know,
Francine
automatically
sorted
order,
and
then
you
can
scroll,
but
you
have
to
keep
writing
to
you.
The
letter
T
or
you
have
to
keep
scrolling
in
the
entire
confusion
with
them.
I.
B
B
C
C
C
A
C
A
More
like
similar
comparison,
I
think
it's
a
physical
out
in
the
design
guidelines
are
things
like
element
node
tree
like
things
that
are
very
generic
right
and
videos.
Hitler
generic
term
stream
is
already
somewhat
specific
source.
Reader
I
mean
compared
to
the
others,
but
I,
don't
know
I,
think
I,
don't
have
a
strong
preference,
I
mean,
let's
just
leave
it
at
that
and
then
make
a
decision
except
maybe
start
an
email
thread
and
then
closed
it
one
way
or
the
other.
So.
B
A
A
A
Facade
is
just
regular,
dll
right,
so,
let's
get
that
gets
deployed.
I
mean
the
only
tricky
part
is.
If
that
assembly
that
you're
trying
to
add,
already
exists
in
desktop,
then
I'm
not
sure
we
can
actually
have
an
appt
local.
There
was.
There
was
a
few
issues
with
problem
of
how
that
works,
but
for
the
majority
of
cases
that
we
have
basically
a
contract
behalf
of
it
is
forwarded
to
to
desktop.
We
can
a
brand
new
types
a
base.
You
only
live
in
that
assembly
we
already
attended
for
sim
Nev.
A
B
A
A
A
The
next
step
would
be
we
just
basically
figure
out.
A
naming.
A
thing
to
me
is
back
level
work
because
it
would
just
go
ahead
and
leave
it
as
it
is
for
now,
and
then
we
can
father
back
and
rename
it.
If
you
feel
we
want
to
change
to
something
else,
it
wouldn't
block
the
work
item
on
it.
Okay,
so
I
should.
B
A
B
A
B
A
The
other
thing
is
Alex
on
West's
team
is
looking
into
how
to
how
to
track
work
that
we
need
to
do
for
desktop.
I.
Think
the
idea
is
that
we
basically
use
labels
on
the
issues,
and
then
there
is
basically
time
review
body
that
walks
over
them
and
make
the
decision
was
to
do
with
those
are
the
report
them
to
the
store,
but
we
don't
put
them
to
desktop
and
if
you
poured
it,
how
we
port
them,
but
I
think
this
is
something
more
like
an
architectural
thing.
A
I
would
just
ping
West
and
say,
like
you
know,
can
we
make
this
a
partial
facade
and
if
not,
why
not?
And
if
we
can't
make
it
a
partial
facade
than
the
question
is,
are
we
willing
to
come
up
with
a
new
contract
just
so
that
they
can
edit
to
death,
so
I'll
be
living
with
effectively
that
it
has
to
be
desktop
4.8
or
something
because
I
agree
with
Chris
stuff,
like
these
Franklin
designs,
that
we
create
these
new
contracts?
Just
so
we
can
add
it
to
desktop.
C
B
This
is
to
be
clear:
this
isn't
I,
don't
have
a
strong
preference.
This
isn't
changing.
The
design
of
the
types
at
all
is
just
a
question
of
where
they
live,
correct,
correct
they
sit
on
top
of
everything
yeah.
If
we
knew
that
we
were
going
to
add
a
bunch
more
things
than
we're.
Gonna
need
a
new
assembly
anyway,
yes,
but.
B
People
just
like
I've
had
some
we've
had
some
requests
for
additional
asynchronous
synchronization
primitives.
We
don't
have
any
of
them.
You
know
concretely
yet,
but
we
had
a
bunch
and
blended
in
like
the
parallel
extensions
extras
package,
and
there
are
some
third-party
libraries
that
provide
such
things.
We've
had
some
both
internal
and
external
requests
for
things
like
an
asynchronous
reader-writer
lock.
So
you
know
if
we
were
to
going
to
go
ad,
something
like
that,
we
would.
It
can
be
done
purely
on
top
of
existing
surface
area.
A
No
for
sure
no,
but
my
point
is
that
I
think
like
a
DS
like,
are
they
logically
cohesive
enough
to
say
I,
don't
know
system
got
threatened,
got
taxed,
God,
foo
and
then
bae?
Your
task
would
go
in
there
or
are
they
all
just
additional
things
that
yep
some
things
may
go
in
system
setting
tasks
and
some
things
may
go
into
I,
don't
know
threading
whatever
other
things
we
have
there
and
I
think
that's
probably
more
likely
right
sure.
A
B
So
this
one
I
I,
don't
know
how
to
deal
with
PRS
like
this.
So
this
one
is
it's
not
adding
public
surface
area,
but
it
is
adding
a
publicly
known
interface
to
a
type,
an
instance
of
which
is
returned
out
of
a
public
API,
the
goal
of
which
being
to
be
able
to
cast
a
type
that
you
get
back
to
this
other
interface.
So
this
particular
guy
has
a
method
called
search.
His
own
method.
That
takes
an
I
read
only
list
and
he
wants
to
be
able
to
pass
a
sorted
list.
B
Skis
collection
or
you
know,
sort
of
this
keys
into
that
keys
returns
an
I
list.
He
wants
to
be
able
to
get
it
as
an.
I
read
only
lists
so
he's
proposed
his
PR.
If
you
look
at
the
files
changed,
it
just
adds
the
the
interface
implementation
yeah.
But
to
do
that,
you
know,
then,
the
code
that
you
write
for
core
effects
will
only
work
and
certain
you
know
only
work
against
certain
implementations
and
not
against
others.
A
Quite
frankly,
I
think
the
value
add
is
so
low
because
you
kind
of
have
to
know
that
you
can
cast
it
on.
I
would
only
this
to
begin
with,
and
it's
in
a
core
type
that
changing
is
relatively
hard
because
they
have
to
touch
it
in
at
these
three
places,
and
on
top
of
that,
I'm
not
sure
how
doesn't
have
any
civilization,
in
fact,
I'm
pretty
sure
probably
does
in
some
cases
that
I
don't
know
I
I
don't
I
mean
is.
A
C
A
A
Yeah,
but
that
I
think
returns
a
read-only
collection,
I,
don't
think
if
it
rains
in
an
interface.
So
we
don't
have
problem
with
the
only
interfaces
you
couldn't
make
the
existing
one
inherit
from
those
which
would
be
the
same
thing
to
do,
and
there's
no
adapter
between
the
so
you
basically
have
to
wherever
you
implement.
I
list
you
can't
have
to
implement.
I
would
only
listen,
no
as
well.
B
A
Yes,
oh
I,
see
what
you're
saying
now,
yes,
I
think,
there's
probably
some
cases
will
be
by
you,
but
you
could
use
an
existing
type
as
the
adapter.
That's
probably
true,
but
we
also
have
I
with
only
collections
of
the
only
thing
you
have
is
an
I
collection.
You
may
not
be
able
to
easily
wrapped
it
in
another.
One
I.
A
B
C
A
C
C
A
A
A
All
right
so.
C
A
A
That's
the
only
problem
for
positive
and
I
compare,
but
if
you
possibly
delegate
delegate
the
sketch
for
every
single
time
right
in
the
kids,
I'm
not
sure
how
these
to
translate
but
I
guess
it's
like
I
think
my
as
far
as
I
know
the.
If
you
do
interface
the
stretch
in
the
tight
loop,
they
host
it
out.
So
it's
only
a
one-time
look
up
because.
A
A
Like
there's
something
I,
don't
know
how
they
compare
when
you're
actually
pause
in
a
comparison,
resistant
I,
compare
I,
think
for
practical
people
inc
purposes,
because
it's
so
hard
to
actually
do
the
translation
from
different
comparison
to
I.
Compare
you
have
to
know
how
to
do
it
because
you
go
with
compare
of
T
DAW
create,
compare
like
it's,
it's
not
great,
plus,
it's
so
common
I
would
say
they're
having
an
overload
generally.
It's
a
good
idea,
see
them
with
your
opinion
on
that
I
mean
I.
B
C
B
A
A
A
B
Were
the
main
ones
that
I
had
top
of
mind?
I,
don't
believe
there
were
any
other
PRS
that
were
blocked
on
you,
but
we
might
take
a
quick
pass
through
there's
a
whole
bunch
of
PRS
like
half
the
PRS
are
waiting
for
feedback
from
Richard
on
kind
of
the
copyright
header,
but
hopefully
we'll
get
word
on
that
suit.
Yeah.
A
B
A
The
issues
that
club
is
terrible-
I
came-
I
really
really
hope,
I
guy
thing
about
cast
a
bunch
of
meetings
over
the
next
week,
so
I
can
actually
sit
in
my
office
for
a
few
hours,
because
I
think
most
of
it
is
just
me
reading
stuff
and
responding
I,
don't
think
there's
any
any
other
way
of
doing
it.
If.
C
C
A
All
right
I
will
take
a
pass
I.
Think
honestly,
most
of
these
things
like
blossom,
we
went
all
that
lists.
The
problem
is
they're
all
in
the
similar
category,
as
in
one
of
them
are
bad.
None
of
them
are
amazing
enough
to
justify
you
know
all
the
ceremony
on
designing
how
we
edit
a
desktop
making
decisions
with
them
and
I.
Think
most
of
our
work
is
kind
of
block
to
have
the
same
passes
around
that
because
I
mean
most
of
them.
A
I
really
just
want
to
say
yet
looks
good,
looks
good,
looks
good
because
they're
all
like
adding
value
of
somewhere.
It's
just
that
the
cost
is
so
high
to
actually
add
them.
Then
it's
always
a
judgment.
Call
is
that
particular
one
nor
off
the
cost
of
doing
it,
and
it
seems
like
a
bad
starting
point,
because
then
you're,
basically
always
start
with
minus
a
thousand
points
which,
for
language
features,
may
be
worth
it,
but
for
simple
API
editions.