►
From YouTube: 2021-01-15-Node.js N-API Team 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
A
A
A
A
B
Yeah,
maybe
we
we
can
take
a
look
at
the
examples
and
yeah
decide
if
we
want
to
implement
this
okay,
so.
A
C
C
A
A
D
D
I'm
wondering
if
the
reference
is
copyable
then
do
we
have
any
idea
that
the
nappy
underscore-
let's
say
those
apis
if
they
are
combo
from
any
thread,
are
rather
than
the
javascript
united
states.
All
of
these
not
be
functions
are
not
safe
to
use
on
the
right
right
other
than
the
javascript
thread.
So
if
the
it's
it's
a
copy
about
them,
blue,
there
might
be
issues
around
these.
These
issues.
A
A
D
A
D
If
the
let's
say
we,
if
we
destroying
the
nappy
reference,
we
are
destroying
the
difference
by
calling
the
actual
pc
function
to
release
the
reference.
So
if
they
are
copy
about
them,
there
might
be
double
releasing
the
same
on
one
same
right,
right
yep.
So
that
may
be
a
problem
where
we
are
on,
like
say
stress,
on
the
working
thread.
Making
the
issue
hard
to
next
make
the
semantics
more.
B
A
So
that's
good!
We
talked
about
those
two.
A
A
B
A
D
A
A
A
Okay,
so
those
I
think
we
can
leave
on
the
we'll
leave
in
here
until
we've
actually
discussed.
What's
going
on
I'd
added
a
few
others
here
which
were
from
across
the
so
let's-
and
I
think
we
touched
on
a
couple
or
two-
but
let's
just
look
at
them
here-.
E
A
A
D
A
D
I've
been
updating
the
pr
just
the
last
yesterday,
so
we
are
including
the
final
all
the
finalizer
finales
in
the
the
change
so
like
we,
we
are
still
able
to
call
in
javascript
functions
in
panelists,
so
there
might
be
exceptions
strong,
like
just
like
say
in
the
series
functions.
So
that's
a
major
change
after
before
compared
to
previous
right.
A
So
the
finalizer
that
will
cause
the
the
runtime
to
to
basically
exit
right.
D
A
A
D
E
A
A
D
D
And
we
are
not,
we
are
not
handling
it
and
handling
those
exceptions,
so
I
feel
the
problem
might
be
defining
if
this,
if
the
existing
behavior
is
malicious
to
learning
codes
right.
A
A
A
Like
and
the
thought
about
that
is
like
we've
often
done
that
like
when
we
introduce
something
which
is
breaking
saying
a
security
release,
we
at
least
let
people
turn
it
off.
So
say
you
upgrade
to
you,
know:
node
16,
but
you've
been
running
with
some
add-ons,
which
you
expect
to
continue
to
run
because
they're
in
api
add-ons
and
they
start
to
stop
working.
A
D
A
And
I
think
I'd
still
not
back
port
it
like
basically
make
it
so
that
it's
you
know
16
and
future
15,
16
or
16
and
future
to
get
that.
D
And
I'm
wondering
how
those
options
might
be
can
be
removed,
since
it's
not
the
expected
behavior
of
our
of
the
node
right
since
the
a
ultimate.
Ultimately,
the
correct
behavior
will
be
throwing
with
the
anchor
exception.
A
D
A
I
think
we've
done
something
similar
great
okay,
so
that's
good
I'll
I'll
put
a
suggestion
in
there
and
we
can
continue
to,
like
you
know,
comment
on
refinements
or
changes
to
that
suggestion
in
there,
and
hopefully
we
can
come
to
agreement
thanks
for
chasing
all
those
down
all
those
different
places,
because
that's
definitely
a
important
one.
A
A
So
this
was,
we
did
discuss
this
a
fair
amount.
Last
time
we
got
and
we
got
some
feedback
from
james
in
terms
of
what
he
had
in
mind.
So
I
don't
think
there's
anybody
pushing
for
renaming
the
symbols.
A
You
know
the
question
I
think
to
go
back
to
is
still
a
little
bit
around.
You
know
how
far
how
quickly
we
want
to
try
renaming
things
or
you
know
there
was
even
the
you
know
can
kevin
was
bringing
up.
We
should.
You
know,
there's
going
to
be
potential
breakage,
so
we
need
to
think
about
that
carefully.
A
I
don't
know
if
I'm
suggesting,
maybe
we
defer
more
discussion
to
this
till
next
time.
At
least
I
have
to
have
to
leave
in
a
few
minutes,
so
I'd
suggest
we
continue
to
discuss
this
in
the
issue
itself
until
next
week.
Is
that
okay
for
everybody.
E
Yeah
and
not
not
to
open
the
discussion
today,
but
I
think
we're
gonna
need
to
determine
who's
gonna,
take
the
lead
and
how
how
this
change
is
going
to
actually
be
implemented.
A
Yeah,
I
think
that
makes
sense,
like
kind
of,
I
think
what
we
want
to
agree
as
a
team
is
sort
of
what
we
think
we
want
to
change
timing
and,
like
then,
who's
going
to
do
the
different
pieces
right
because
right
right,
I
could
see
that
you
know
the
first
easier.
One
is
well
we'll
go
through
the
docs,
and
maybe
you
know
reword
so
that
it's
clear
it's
node
api
versus
anything
else.
Right
and
then
you
know
separately.
What
would
be
the
next
step?
So
we
can.
E
A
Okay,
so
is
this
one
was
that
the
one
we
just
looked
at.
A
This
one,
what
I
haven't
spent
enough
time
to
understand
is
like
is,
is
that
const
marking
thinks
kant's
gonna
break
anything,
and-
and
I
guess
the
reason
I
added
on
the
list-
that
for
people
to
think
about
is
the
objects.
Aren't
cons
like
the
the
methods,
are
actually
changing
things
within
the
objects.
A
So
I
wanted,
you
know
more
people's
views
on
whether
you
know
that
that's
that
makes
sense
in
terms
of
you
know
us
saying
yeah
these
these
are
mark
cost
because,
like
technically
you
know
a
const
pointer,
for
example,
you
can
chain,
you
can't
change
the
pointer,
but
you
can
change
indirectly
through
that
pointer.
What
the
sort
of
state
is
right.
B
Yeah
we
we
have
for
for
this
yeah
and
yeah.
B
B
It
does
not
introduce
changes
and
but
yeah,
I
started
the
sea
last
week,
and
so
there
is
in
the
paragraphs
there
is
a
discussion
started
buying
umbrella
yeah.
So
I
think
that
the
the
right
place
to
discuss
is
in
the
dpr.
At
this
point
and.
B
Yeah
we
we
can
continue
so
in
this
pr
and
to.
A
B
A
Basically
say
that
in
here,
where
are
we
so
here
this
one
I'm
gonna
be
you
know,
discussion
is
discussion,
taking
discussion
taking
place
in
pierre,
going
to
close
this.
A
Makes
sense
right,
like
yeah
the
discussion
started
there,
we
can
close
it
out
there.
We
don't
necessarily
need
it
on
our
agenda.
So
that's
good,
okay,
so
yeah.
At
this
point,
I
I
have
to
jump
to
another
meeting,
so
I
think
nikola
you
were
gonna.
Take
over.
You
know
continuing
going
through
the
agenda
right.
A
Okay,
I
will
I'm
gonna
stop
sharing.
I
will
make
you
the
chair,
make
the
host
so
that
it
doesn't
stop.
When
I
leave
and
thank
you
very
much
for
taking
over
and
I'll
watch
the
video
afterwards
and
and
talk
to
everybody.
C
C
B
Okay,
see
you
these
are,
but
I'm
okay,
yeah-
and
I
didn't
have
time
for
this
and
and
you
I
have
not
looked
at.
B
Oh,
these
is
michael
work,
so
yeah.
We.
I
think
that
we
need
to
discuss
with
him
or
next
meeting
and.
B
B
Okay,
we
just
discussed
this.
Is
there
an
issue
that
you
won't
discuss.
C
I
I
don't
have
any
necklace,
okay
and
you
will
join.
B
B
Okay,
and
is
there
some
something
else
on
another
dawn
api,
or
do
you
want
to
discuss
about
hiding.
B
Okay,
so
we
have
okay,
the.
B
B
E
Issue
maybe
do
a
search
for
headers
nikola.
B
Yeah
yeah
not
be
haters
so,
but
I
don't
remember
where
it
is.
If
in
not
the
done
api
or
not
so,
okay,
okay,
I
think
that
I
found
phone.
Oh
okay,
so.
B
So
for
now
yeah,
I
think
that
I
can
add
these
files.
Okay,
and
how
do
you
want
to
proceed
so
just
copy
our
headers
or
do
we
need
to
automate
something.
E
I
would
like
to
see
nikola
about
implementing
github
actions
to
automate
this.
B
Yeah-
I
I
was
thinking
about
this,
but
I
I
I
don't
have
many
experience
about
guitar
actions
and
going
to
try
to
to
to
yeah
to
do
this
just
to
do
some
experiments.
B
So
my
idea
is
essentially
that
when
we
have
a
new
things
on
on
the
in
api,
either
files,
we
need
to
take
that
and
create
a
new
version
of
this
package
and
publish
on
npm
and
if
it
happen
automatically
could
be
great,
okay,
yeah.
Maybe
we
can
publish
manually
but
yeah.
B
If
we
can,
we
can
take
the
device
and
yeah
push
on
the
git
automatically
yeah.
It
could
be
good
for
me
very.
E
Good,
okay,
that
that
that
sounds.
That
sounds
really
good
nicola.
If
you,
if
you
create
an
issue
on
this
new
repo
and
if
you
list
the
steps
that
you
would
like
to
have
happen,
that
the
triggers
and
the
results
that
sort
of
thing,
if
you,
if
you
describe
it
as
at
a
high
level
in
an
issue
and
then
ping
me
on
it,
then
I
I
would
be
delighted
to
to
look
at
creating
a
github
action
to
implement
it.
B
Yeah,
okay,
so
later
yeah
I
will
and
the
readme
file
and
and
yeah
got
the
content
and
continuity
and
and
then
open.
That
is
a
new
new
issue
and
describe
yeah
what
yeah
I
want
to
do
and.
B
And
ping
you
on
the
on
the
on
the
on
the
edge
okay,
it's
okay
for
for
me
and
michael
yeah,
call
it
the
note
the
api,
so
here
in
these
are
april,
we
don't
have
any
problem
about
the
name.
B
Yeah
yeah
yeah,
okay,
yeah.
I
agree
on
on
the
change,
the
name
but
yeah
it's
a
little
difficult,
but
okay.
So
it's
a
process.
I
don't
know
this
was
the
last
thing
for
me.
If
you
don't,
I
don't
know
if
you
have
something
to
discuss
lucas
jim.