►
From YouTube: NGS weekly meeting #18 - 2022-02-13
Description
Project website - https://ngs-lang.org/
Discord - https://discord.gg/6VqgcpM
A
B
A
C
C
C
A
A
C
A
B
C
A
A
B
A
A
Because,
as
ricardo
mentioned
on
previous
meetings,
it
would
be
very
nice
to
have
released
so
before
we
are
making
this
release.
I
would
like
to
finish
the
script
and
I
want
in
this
meeting
to
go
over
like
other
things
and
then
dive
just
a
bit
deeper
into
the
release
script
and
see
where
we
are
standing
there
and
what
are
the
technical
issues
and
how
that
goes
so
unrelated
to
release
script
and
anything
else.
A
A
A
Most
of
the
discussion
goes
like
about
details
and
how
better
to
implement
that
the
current
view
on
that
is
that
it
will
be
without
new
syntax
and
without
changing
any
default
behavior
and
we're
kind
of
trying
to
figure
out
the
details
of
the
implementation,
so
ricardo.
We
are
now
advanced
users
of
github,
because
it
was
the
first
discussion
that
I
created.
A
A
A
They
have
this
thing
when
you
can
do
my
func
yeah
and
then
provide
the
closure
and
code
here
and
the
main
problem
with
this
thing
is
in
ngs:
that's
a
bigger
syntax,
because
you
can
have
an
if
you
have
condition
and
then
okay,
so
my
funk,
this,
that's
the
yes
close
of
the,
if
that's
for
sure,
but
now.
What
is
this
is
this?
Does
this
belong
to
my
funk?
Or
is
it
the
else
part
so.
A
So
meanwhile,
nothing
nothing
happened
here
and
just
does
have
somewhat
similar
features.
So
meanwhile,
meanwhile,
nothing
happened
with
that.
It
was
a
bit
of
discussion,
but
let's
say
if
the
demand
will
be
high,
we'll
try
to
solve
that
too.
I
just
currently
don't
see
straightforward
solution
to
that.
A
Okay,
pcre
call
outs,
that's
feature
request,
but
also
we
are
like
waiting
for
more
demand
on
that.
It's
like
in
general
pcre
is
a
library
which
ngs
already
uses
it
already
exposes
some
functionality.
I
don't
have
any
conceptual
problem
with
exposing
more
functionality
of
the
same
library
we
are
already
using.
A
A
I
said
pearl
grammars,
it's
actually
rakugramos,
but
I
guess
that
at
the
time
that
I
looked
at,
that
it
was
pearl
six
grammars
and
now
pearl
six
is
actually
called
raku,
so,
okay
so
fix.
I
fixed
that.
I
just
took
it
from
here
and
paste
it
into
wiki
requirements
yeah
another
discussion,
not
particularly
interesting.
A
A
C
C
Hi
hi,
just
one
quick
remark
about
this:
what
I
call
this
trailing
closures,
stentax,
I'm,
okay,
that
you
know
this
will
impact.
You
know
how
you
do
things
in
nts,
so
I'm
okay
to
use
this.
You
know
this
do
things
and
do,
and
with
I
mean
you
talk
about
this,
I
think
this.
This
would
be
just
fine.
Actually,
you
know,
but.
C
A
Yeah-
let's
do
this
for
a
moment,
so
my
funk
do
and
expression
here
and
so
what's
yeah,
I'm
talking
look.
I
think
you
already
know
that,
but
I
I
will
be
talking
about
the
potential
viewers
of
this
video,
so
what
we
have
here
like
unlike
other
languages.
First
of
all,
there
is
a
keyword
between
the
the
braces
and
the
expression,
but
what's
interesting
that
you
can
actually
continue
and
pass
several
arguments
like
this.
A
Instead
of
do
you
can
use
with
which
I
think
was
my
mistake,
because
I
don't,
I
think
it's
actually
the
only
place
in
ngs
when
you
have
two
things
like
keywords
or
or
something
like
that
which
do
exactly
the
same
thing.
I
think
I
think
it's
just
wrong
on
on
on
the
level
of
like
when
you
think
like
how
different
people
will
be
using
this
language,
and
then
you
know
yeah.
C
A
C
A
A
A
Okay,
that's
the
script,
but
we'll
get
into
this
in
a
moment,
syntax
yeah!
I
was
actually
okay
so
with
and
do
they
are
like
completely
aft
after
this
place,
nobody
is
able
to
distinguish
and
all
of
this
by
the
way,
there's
also
arrow,
but
it's
like
it's
completely
deprecated
already
it's
when
you
have
like
named
parameter,
but
it's
like.
I
duplicated
that
already
so
reason
do
they
are
here.
A
They
are
function
called
external
argument
in
our
syntax
and
and
as
you
can
see,
we
have
other
function,
call
arguments
here
and
oh,
what
happened?
Oh,
no,
okay
and
after
we
have
this
external
argument,
it's
just
appended
to
the
same
place
and
from
here
on,
you
just
can't
distinguish
any
of
this
stuff.
A
A
Okay,
by
the
way,
if
there
are
like
there's
like
a
particular
topic
which
is
like,
maybe
doesn't
fit
the
weekly,
we
can
do
another
meeting.
We
can
maybe
do
like
right
after
the
weekly
or
some
other
time
so
feel
free.
Everything
is
up
for
discussion
and
it's
good
to
have
okay.
So
for
now
the
script.
What
is
interesting
in
the
script
main
functions?
That
would
be
the
entry
point.
A
A
A
A
A
C
A
C
When
you
write
a
a
bash
comments
and
also
the
three
directions,
I've
seen
some
of
the
directions
in
ngs,
but
not
all
bash
things
are
supported,
and
this
might
be
a
in
an
interest
to
some
people
who
would
want
to
switch
to
ngs
because
they
are
used
to
bash
and
and
if
they
need
it,
they
have
to
lose
some
flexibility
on
the
command
syntax
part
they
may
cause
some
problem.
I
mean
that's
what
I
can
think
of
right
now.
A
A
B
A
A
A
So
what
is
happening?
What
is
happening
here,
this
percent
syntax
is
actually
saying.
Okay,
that's
the
command,
just
don't
run
it
now.
Okay,
so
you
you
have
a
reference
to
the
command
which
is
like
ready
to
run,
but
you
can
also
modify
it
before
running
so
what's
happening
here,
run
run
is
called
with
with
the
command
to
run
actually
it's
commons
pipeline
because
there
could
be
pipes
in
there,
so
it
gets
the
wall
pipeline.
A
A
Yeah,
okay,
worn
is
just
something
which
is
go.
Message
goes
into
standard
error,
nothing
particularly
interesting.
So
what
what
are
we
doing
here
when
we
do
release?
I
expect
all
the
commits
to
be
on
the
dev
branch,
and
I
expect
there
would
be
no
commits
on
master
branch
which
are
not
on
the
dev
branch.
A
A
A
A
A
So,
what's
interesting
here,
git
diff
with
exit
code
can
tell
us
if
the
file
was
changed
and
what's
interesting
here
from
ngs
side.
Is
that
there's
an
option
which
says:
ok
and
that's
a
list
of
exit
codes
on
which
not
to
throw
an
exception
so
for
comments
that
ngs
doesn't
know
about
non-zero
exit
code
would
be
an
exception
so
about
git
diff.
It
just
doesn't
know
yet
so
I
needed
to
list
it
not
to
have
an
exception
and
then
conversions
into
boolean.
That's
the
regular
stuff.
Zero
is
true.
A
A
Without
and
if
you
would
a
dollar,
that's
see
it's
already
processed,
so
it's
processes
pipeline,
not
comments,
it's
processes
because
they
were
running
and
let's
see
what
they
did
yeah.
So
we
have
redirects
here
and
file
descriptor,
one
and
stuff
like
that.
Okay,
anything
else
before
we
continue
with
the
script
nope,
okay,
so
yeah.
So
while
I'm
working
the
script,
I
also
seen
you
know
how
like
there
are
quite
a
few
ugly
parts
which
I
will
need
to
fix,
but
there
are
also
quite
a
few
good
parts.
A
So
in
change
log
we
have
unreleased
at
the
top
change
log.
Okay,
so
we
have
it
here
because
unreleased
it
comes
like
instead
of
the
date
which
will
have
another
versions.
So
during
the
release
process
it
should
be
substituted
with
the
date.
So
how
we
do
that,
I
added
a
replace
function
which
works
with
file
now,
so
it's
in
in
in
place
replace,
so
it
just
takes
the
unreleased
and
places
the
date
over
there.
A
A
A
A
If
any
of
the
elements
is
matching
this
pattern-
and
we
are
just
looking
if
we
have
our
commitment
there
so
after
it's
there,
okay,
so
what
happens
if
it's
all
like
over
and
no
and
the
body
is
still
failing?
Well,
it's
an
exception.
It's
retry
exception.
So
no
nothing
continues
here.
So
then
we
need
to
wait
for
bill
to
finish
a
very
similar
thing.
A
What
I'm
thinking
is
actually
to
replace
this
github
command
line
with
something
else,
because
it's
it
seems
absurd
to
me
that,
as
this
guy
needs
my
login
to
work
with
the
repository,
which
is
public,
I
think
I'll,
probably
just
use
the
rest
api
they
provide.
I
think
I
will
be
able
to
fetch
what
I
need,
because
you
know
if
you,
if
you
go
to
the
website,
you
don't
need
to
be
logged
in
to
see
all
this
actions
and
flows
and
all
that.