►
From YouTube: 2019-10-21 C/C++ SIG
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
C
B
B
C
B
B
B
So
talk
to
us
a
meal
of
light
and
I
think
we
can
keep
the
current
time
and
they
blade
her
it'll
be
too
early.
I
know,
please
let
us
know
I
just
want
to
make
sure
that
he
you
will.
Let
us
know
when
the
you
want
to
change
the
time.
Okay,
I
will
yeah
and
I
have
only
one
topic
today,
so
I
won't
talk
about
the
PRS
I
start
to
receive
feedback
from
people
on
the
folder
structure.
B
B
B
And
so
the
first
PR,
it's
really
easy,
trying
to
hold
the
folder
change
like
the
folder
structure
and
I
think
I
I'm
trying
to
follow
two
things:
one
is
a
bag.
Another
thing
is
the
experience
that
we
learned
in
the
Python,
SDK
and
I
started
to
receive
the
feedbacks
from
mail
and
and
Josh
I
think.
So
let
me
explain.
A
B
The
first
thing,
in
my
mind,
is
we
want
to
keep
this
API
and
SDK
separate
and
I
interpreted
this.
You
know
way
that
the
API
and
SDK
should
be
in
totally
like
separated
packages
and
they
have
their
own
build.
So
if
you
take
this
open,
telemetry
product,
no
one
to
say
I
want
to
build
my
own
SDK.
They
can't
follow
this
I,
stick
a
structure
and
create
their
own
version.
Without
seeing
oh,
like
the
open
country,
API
and
I,
Steve,
Heather
and
tango
seems
like
folks
working
on
this
open
country.
It
has
fast
product.
B
They
try
to
promote
the
SDKs
of
first-class
citizen
so
on
to
make
sure
that
clear
separation-
and
we
don't
put
any
preference
over
our
SDK
with
this
I-
want
the
API
to
be
in
its
own
package
and
I
steal
it
be
in
its
own
package
and
I
understand
having
a
top-level,
a
good
folder
build
will
be
convenient
and
I'll
try
to
achieve
that.
But
meanwhile,
I
I
think
having
that
separation
is
going
to
help
us
to
to
have
a
very
clear
contrast
between
the
API
SDK,
including
all
the
tooling.
B
B
Country
they
sit
inside
the
same
thing
because
I
buy
my
team,
like
they're,
backed
by
the
same
set
of
authors.
So
it's
us
and
simmer
like
license.
We
produce
both
the
ETA
and
is
DK,
but
we
always
keep
in
mind
that
our
API
package
is
three
customers,
but
that
I
speak
here
is
only
the
recommended.
I
speak
about
people
like
different
burners.
They
can
configure
their
own
stuff
without
being
boring
like
we
try
to
make
this
I
see
as
the
official
standard
we're.
D
B
I
I,
don't
know,
probably
not
because,
like
probably
because
my
experience
implies
me
so
the
API
package
actually
is
not
the
pure
API.
It
has
some
implementation.
Freedom
Hall,
like
you,
can
imagine
like
the
know
of
very
fast
implementation
for
tracer
and
for
metrics
aggregation.
But
meanwhile,
in
order
for
people
to
use
the
pure
API
package
and
still
make
a
of
like
a
working
application,
we
got
to
take
the
trace
contacts
and
being
able
to
manipulate
and
problem,
probably
get
them
properly.
D
B
B
D
B
D
B
Know
everything
just
got
up
on
the
floor
and
the
performance
is
super
good.
So
you
basically
don't
do
anything
that
or
propagating
the
twist
contacts,
and
why
do
we
do
that?
Because
you
know
I,
don't
have
a
function,
your
service,
that
that
is
compliant
to
the
trace
contexts
back.
You
want
to
be
able
to
understand
that
incoming
trace
ID
and
if
that
trees
ID
is
invalid.
We
use
an
outgoing
one.
It
got
to
generate
a
new
phase
idea,
so
all
the
like,
like
choice,
compacts,
parsing
and
sterilization
logic,
it's
between
the
API
package.
Yes,.
D
So
I
think
that's
that
would
still
be
compatible
with
making
something
header
only
like,
but
to
know
if
it
doesn't
need
any
external
dependencies
or
anything,
and
you
know
there's
a
lot
of
like
fairly
large
header.
Only
libraries
like
you
know,
just
look
at
boost
and
like
the
whole
azo
networking
library,
like
nearly
all
that
is
header
only
so
this
would
still
be
pretty
manageable,
as
I
had
our
only
API
library,
mm-hmm.
C
I'm
I
have
some
concerns
about
what
is
the
build
going
to
look
like
for
users
of
the
library
right
like
even
if
it's
a
header,
only
library,
you
still
need
build
dependencies
on
the
headers.
So
if
you
have
a
single
repo
like
we
have
now
with
a
API
directory
and
SDK
directory,
do
you
add
that,
as
like,
like
basil,
sub
repositories
with
with
like
a
prefix
cut
off
or
yeah
I,
don't
know
this
kind
of
came
out
with
like
what
do
we
do
with
see
make
like?
C
Do
you
have
a
single
top
level
build,
or
do
you
have
like
sort
of
two
top
level
builds
in
the
two
subdirectories?
If
we
end
up,
you
know
packaging
for
like
Debian
or
some
things
you
would.
You
have
separate
Debian
packages,
full
API
and
SDK.
B
D
C
Definitely
doable
would
see
make
because
it
yet
you
can
have
those
top-level
options.
I'm
just
wondering
like
if
later
will
end
up
splitting
into
two
repos
or
it'll
just
be
might
be
a
little
bit
messy
it'll.
Take
some
discipline
so
that,
for
example,
the
API
doesn't
accidentally
depend
on
the
SDK.
B
Let
me
explain
title
work,
although
I
understand
this
is
talking
about
C++,
but
I
probably
inherited
a
lot
of
like
ideas
from
the
title
work,
and
so
here
we
got
this
open,
clamp,
API
and
SDK
package
and
the
reason
we
have
this
instead
of
either
for
people
to
read,
and
we
don't
use
that
for
import
past.
It's
just
a
folder
and
also
Python
package
structure,
actually
encourage
people
to
put
instead
of
underlined.
So
this
is
something
where
I
saw
like
the
comment
from
a
male,
although
I
think
it's
a
great
idea.
B
I
want
to
have
like
see
like
same
human
tation
wall
having
Python
using
functions
like
foreign
function
interface
as
a
test
harness
because
it's
much
simpler,
read
test
cases
either
the
C
bindings
and
from
that
API
package.
The
top-level
thing
is
called
open
country
folder,
and
we
don't
API
folder
because
most
of
the
user,
we
want
them
to
import
from
open
country
dot
trace
instead
of
open
claims
without
freestyle,
API
or
dot
EDI
adultress,
which
probably
like
too
long
for
them
and
and
this
one
you
can
see
like
it's
a
full
Python
package.
B
It
has
its
own
Britney
and
own
changelog
and
we
can
release
them
separately
from
that.
So
in
this
way
we
give
you
a
feeling
that,
although
we're
will
hear
both
I
speak
but
we'd
like
we
never
try
to
tie
them
together
and
you
can
build
your
own
as
you
can
just
replace
this
SDK
and
the
inside
nice
DK.
We
didn't
wait
for
this.
Open
country.
Dogs
is
DK
in
this
way
when
people
try
to
write
code,
it's
very
clear,
better
they're,
pure
API
or
SDK.
B
B
So
what
would
we
expect
you
to
do
is
to
just
import
from
open
climb
to
a
trace
and
open
country
contacts
and
use
all
the
API
to
generate
the
span.
But
this
four
lines
of
code
are
actually
they
like
the
first
three
lines:
they
import,
the
ice-t
have
functionality
and
the
last
line
how
the
API
hey.
Please
use
this
ice.
Tk
tracer
as
the
tracer,
this
is
the
actual
functioning
tracer,
otherwise,
it'll
be
the
know
how
tracer
so.
C
B
E
In
that
sense,
we
could
have
had
just
one
package
and-
and
we
know
that
when
we
add
new
API
will
go
into
interface
first
and
we
have
to
do
the
implementation
of
concrete
functional
class
as
well
as
updating
the
pure
null
object
pattern:
a
logger
tracer
with
a
new
method.
For
that.
With
that
work,
like
with
one
package
only.
B
B
B
C
B
Like
in
Python,
we
can
take
a
look
like
in
the
extension
packages,
so
there
are
all
the
plugins
we
have
this
year,
Greg's
father
and
we
were
trying
to
add
the
zip
things
fodder.
For
this,
other
specific
is
color.
We
got
kicked
out
so
any
like
vendor
specific
same
expect.
Driver
error
monitors
they
should
move
away
to
their
own,
like
github,
stash.
C
B
Ok,
feedback
and
with
that
consider
like
for
the
scenic
I,
am
not
familiar
Simic,
so
I
probably
live
in
the
old
world,
where
people
write
their
like
manual,
make
file
and
also
config,
so
I
haven't
been
for
several
years,
so
bear
with
me
and
I
assume
that,
even
if
you
have
the
top-level
Simic,
let's
say
he
and
I
sneaked
a
package
dividual
a
they
come
work
as
a
separate
package.
Would
Simic
provide
the
functionality
where
you
have
a
top
level
like
simple
file
that
you
can
basically
call
I
want
to
build.
D
So
with
seeming,
you
can
include
like
some
products
but
like
the
cmakelists
file,
mister
product
of
function
as
its
own
independent
teammate.
So
there
can
only
when
you
in
the
top-level
see
make
you
have
to
declare
the
project
and
you
set
things
like
the
minimum,
see
make
version
and
stuff
like
that,
so
that
that
doesn't
get
like
copied
into
the
other
subdirectory
seen
eggs
I
see.
C
B
B
B
We
have
this
top
level
like
talks.
This
is
the
single
interface
where
you
run
and
you
build
everything
and
test
everything
and
you
can
add
different
flavor
better.
You
won't
run
tests
only
or
it
won't
run
entire
cycle,
and
also
for
for
the
usage
you
didn't
have
to
be
install
everything
you
just
have
to
be
install.
The
ice
became
I
think
it
actually
has
the
dependency
on
a
TI,
so
it's
pretty
straightforward
and
I
I
was
assuming
that
he
is,
it
was
fast
we
can
achieve
the
similar
thing.
E
D
It's
most
commonly
used
on
Windows,
like
I,
haven't
seen
it
used
a
lot
on
Linux
like
for
my
experience
like
most
people
that
are
building
with
the
open
tracing
stuff.
They
just
they
they're
using
like
some
Ubuntu
or
something
common
like
that,
and
they
just
want
to
run
CMake
point
into
the
directory.
Make
install
and
then
expect
everything
to
be
set
up
correctly.
A
lot
of
the
pain
point
is
managing
dependencies
and
things
like
that,
especially
if
you
include
like
GRDC
and
protobuf
for
you
to
generate
that.
C
Seem,
but
does
the
open
tracing
thought
have
to
be
installed
system-wide,
or
can
you
do
like
a
mundo
build
or
external
build
whatever
the
:
C
make
there's.
C
I
think
it'd
be
nice
to
support
BC
package.
I
have
heard
it
mentioned,
also
Conan,
which
hasn't
come
up
today,
but
I've
heard
other
people
mentioned
it'd,
be
nice
to
support
all
these
things,
but
not
require
them.
Ok,
on
my
side,
we
I'd
really
like
to
have
it
work
with
basil
and
the
way
basil
works.
Is
you
essentially
point
to
the
source
code
of
things
you
depend
on
I,
think.
E
C
Think,
because
of
the
state
of
Sybil's
plus
and
like
a
previous
person
was
saying
like
it
doesn't,
you
know,
come
with
its
own
packaging
system.
We
need
to
support
a
handful
of
these,
or
at
least
not
be
hostile
to
supporting
new
ones
right,
so
that
we
shouldn't
require
basil.
We
shouldn't
require
CMake.
We
should
definitely
support
C
make
because
it
seems
to
be
what
customers
want.
C
D
B
C
Another
one
both
both
of
these
systems
essentially
need
you
to
put
their
files
in
every
sub
directory.
I
said
so
having
a
central
place
doesn't
actually
help.
You
can
have
like
libraries
and
things
in
there,
but
then
again
you
have
this
thing
of
like
does
open
open
since
it's
a
peeps
right,
open,
telemetry
API
now
like
depends
on
this
like
see
a
sub
directory.
That's
outside
of
its
module
like
we're,
gonna
have
to
be
a
bit
disciplined
about.
Are
we
treating
these
as
separate
packages
inside
a
repo
or
like?
C
Are
they
sub
repos
or
like
what
it's
see
make
lists
txt?
But
yes-
and
this
was
kind
of
my
question
earlier
like
do
we
treat
this
as
two
separate
packages
that
have
separate
build
systems
or
do
we
treat
this
like
one
overall
thing,
but
we're
just
very
careful
about
dependencies,
not
happening
in
the
middle?
You
know
what
I
mean
like
so
API
doesn't
accidentally
depend
on
SDK
yeah.
D
So
my
preference
would
be
just
to
have
like
one
teammate
project
just
because
I
feel
like
treating
them
as
separate
projects.
Gifts
can
get
kind
of
messy
but
see
make
like
using
external
products,
and
things
like
that
is
somewhat
difficult
so,
like
just
having
like
you,
make
list
text
in
the
root
directory
and
then
having
options
and
a
you
know,
if
conditional
statements
to
not
install
the
SDK,
if
you
don't
ask
for
it
like
that
would
be
my
preferred
way
of
doing.
B
It
for
release
freedom.
How
if
you
have
a
like
denim
package,
people
will
either
have
this
like
pure
package
compiled
from
source
where
they
can
put
info
flags,
say:
I
want
API
only
or
I
want
both
or
there
will
be
pre-built
binary,
which
is
talking
either
as
pure
API
or
SDK
right
yep
and
the
works
for
me.
Yeah.
B
C
We
can
I
think
start
off
the
way
Python
did
where
you
put
all
of
the
extra
exporters
into
into
the
same
repo,
at
least,
but
then
again
you
have
to
be
disciplined
so
that
you
don't
sort
of
add
accidental
dependencies.
Like
oh
now,
Hotel
API
depends
on
Geo
PC
mm-hmm.
C
D
C
B
B
Challenge
like
I
observed,
the
IMP
isin
is
being
talked
about,
like
people
try
to
include
something
it
could
be
any
user
or
they
could
be
SDK
developer
and,
at
least
for
Tizen
were
we're
facing
a
difficulty,
because
some
people,
when
they
become
the
I,
speak
head,
they
won't
say
I,
don't
want
to
like
Fremont
all
the
wheels
from
that
secret.
I
just
want
to
override
my
part.
So
once
we
include
some
reusable
components
from
the
SDK
and
do
whatever
specific
stuff
I
want.
D
Of
the
example
yet
so
I
would
think
they
did
getting
installed
into
a
different
public
header
directory.
So
when
you
run
make
install
and
you
if
you
include
the
SDK,
then
if
you
look
in
the
slash
user,
slash
local
slash
includes
slash
open
telemetry
you'll
find
some
of
those
SDK
parts,
which
means
we
have
to
look
very
disciplined.
B
D
C
C
Also
basil
has
this
concept
of
you:
have
a
single
top
level
workspace
file,
which
sort
of
defines
this
is
like
a
module
or
repulsive
sub
repository,
whatever
they
call
it,
but
then,
in
every
directory,
where
you've
got
stuff
to
build,
you
have
a
build
file
right
and
also
you
probably
have
a
sea
make
list.
But
this
is
what
Ryan
was
saying
like
you,
like
sort
of
include
these
recursively,
but
they
don't
like
this
list
here,
doesn't
specify
the
top
level
set
project.
E
G
B
Here
so
a
male
will
put
this
open
llama
tree
and
contacts
as
the
siblings.
What
does
it
mean
that
open
climb
tree
faller
just
for
holding
all
the
build
files
or
inspect
the
contacts
to
be
under
open
television?
So.
C
What
what
I
was
trying
to
illustrate
here
is
you:
have
this
API
and
SDK
a
sub
directories
sort
of
at
the
root
of
the
repo
we
split
it
up
into
including
source?
That's
what
Ryan
was
saying
about
keeping
the
public
headers
separate,
which
I
agree
with,
and
then
basically
this
include
all
of
its
children
get
copied
to
use
a
local
include
right,
so
you
want
a
namespace
open,
telemetry,
and
then
you
have
these
directories.
We
didn't
have
like
a.
We
have
the
actual.
B
D
E
C
C
E
Alright
yeah,
maybe
I
just
had
it
in
cursive
some
stuff
that
I
think
might
be
worthwhile
adding
at
the
top.
Well
examples
you
know
definitely
foresee
make
Vera
dot
seemed
like
files,
which
might
not
be
like
utilities
that
you
write
yourself
that
would
do
like
fine
TC.
My
log
make
Debian
package
Mac
rpm,
something
that
is
not
standard.
E
A
part
of
foresee
make
like
put
it
in
my
c-max
specific
scripts,
a
reusable
pieces
that
might
be
included
from
the
top
levels
in
my
quest
and
I
assume
that
perhaps
I'm
not
familiar
with
base
or
but
isn't
that
something
that
is
useful
for
basal
as
well.
I
think
I
said
something
like
this
in
chromium
source.
B
B
D
If
you
put
the
test
next
to
it
like
that,
it
can
because
sometimes
you
the
test
can
actually
include
like
a
lot
of
utility
functions
and
stuff
like
that.
That
sort
of
function
like
their
own
sort
of
packages,
so
I'd
I,
prefer
having
like
a
directory
and
then
the
Tesco
and
they're
similar
to
like
how
envoy
lays
out
its
project.
Yet
so
envoy
and
Java
key.
C
Code
in
my
experience,
this
is
usually
not
a
problem
because
your
context,
tests,
utils,
are
kind
of
specific
to
context
so
well,
sometimes
they
can
span
multiple
tests
like
yeah
but
like.
If,
if
later
you
write
a
test
that
deals
with
context,
you
will
include
the
context,
library
and
the
context
test.
Utils
well,
like
objected
in
being
Basel.
Everything
is
a
very
fine-grained
libraries,
like
basically
every
CC
fault,
yeah.
D
There's
like,
but
the
utils
like
it
might
not
be
specific
to
context
like
just
an
example
is
like
one
of
the
tests
we
run
with
our
tracers
as
we
start
up
like
a
mocked
ratio.
That's
the
muck
collection
point,
that's
written
and
go
so.
There's
like
this
whole
like
sort
of
go
project
within
the
test,
folder
enough.
D
C
This
sort
of
context
test,
alright,
so
I
think
a
good
argument.
There
is
when,
when
you're
building,
essentially
like
a
ignoring
basal,
when
you're
trying
to
build
something
like
a
debian
package
where
you
have
like
a
lib
hotel,
SDK
dot,
ISO
right,
you
don't
want
test
code
in
it.
And
if
you
want
a
library
of
test
utils,
then
we
have
to
think
about
like
what
are
the
public
headers
that
get
exposed.
And
then
what
goes
into
that
library,
yeah
yeah.
D
C
C
D
D
E
I've
been
dealing
with
so
much
decay
for
four
years
we
have
about
600
to
800
tests
across
about
70
files
and
in
our
use
case,
unit
tests
and
functional
tests
end
up
about
60
to
70
files
in
a
flat
organized
manner,
although
for
the
including
source.
Yes,
we
kind
of
follow
exactly
the
same
way
out.
As
you
know,
three
layout
for
the
test,
it's
just
like
is
there
a
possibility
that
our
test
code
base
grows
large
enough
to
require
a
structure
like
sure?
E
C
C
Sodium
then
lead
a
little
bit.
There
is
with
basil
the
directory
structure,
defines
kind
of
packages,
and
it
does
end
up
essentially
like
a
customer.
Using
basil
will
have
two
right
paths
that
match
the
directory
structure
inside
the
repo.
So.
D
C
B
C
That
would
be
great
I
have
one
of
these
photo
consensus
and
even
one
that
lives
in
a
separate
repo
just
to
show
like
sort
of
from
scratch
like?
How
do
you
do
that?
How
do
you
get
it
to
build
and
I
think
having
an
example
like
that,
will
inform
like
what
you
want
the
structure
to
look
like.
B
Think
the
kind
of
structure
looks
good,
so
forecast,
I
I,
don't
know
whether,
like
we
got
people
all
great,
do
we
still
keep
the
hierarchy
or
make
it
a
plan?
I
have
a
trouble
like
naming
things.
So
if
we
put
data
as
a
plan
folder,
then
how
do
I
name
the
context
test?
Should
they
be
call
like
ot
contacts
test
or
something
I,
don't
know.
B
E
E
E
I
know
scan
and
see
because
so
we
didn't
discuss
this
like
about
client
format.
I,
don't
really
want
to
have
a
religious
debate
about
what's
best
coding
style
like
I'm,
open
to
anything
I
just
suggesting
that
maybe
we
should
just
converge
on
crying
format,
because
we
can
also
automate
that
as
part
of
command
line
experience
as
well
as
the
raw
plugins
for
that
for
what
we
just
do.
The
visual
studio
code
bi,
whatever
eclipse
acidity
that.
D
Sounds
good
to
me,
I
think
you're
posting
about
like
following
the
CPB
core
guidelines,
as
that
was
good.
I,
don't
think
they
have
a
naming
convention
as
part
of
the
guidelines.
I
used.
That's
like
one
piece
deciding
on
what
naming
convention
we
want
to
adopt.
E
E
D
H
E
Available
who
designs
an
extension
for
certain
exported
for
certain
system
and
then
that
system
do
they
use
a
lot
of
the
format
of
Linux
format,
whatever
we
can
always
say
that,
there's
a
dot,
clang
format,
file
for
that
directory
and
that
extension,
export
of
developer
company
follows
that
standard
and
if
you
want
to
contribute
in
there,
you
just
you
know,
use
that
local
client
format
other
than
that
the
root
level
flying
format
would
apply.
But.
E
D
E
E
C
Interferes
with
the
build
system
and
stuff
I
think
we
should
encourage
people
to
keep
things
in
separate,
repos
and
I.
Think
with
the
client
format.
I
agree
that
it
should
be
automatic,
I
think
it
should
be
enforced
as
part
of
CI.
Ok
and
yes,
I,
don't
super
care
about
the
specifics.
As
long
as
like
you
said,
there's
a
script,
so
it
right.
Yes,
yeah
with
open
census.
We
have
a
tool,
slash
format,
door,
SH
and
it
just
does
everything
it
even
fixes,
like
common
typos,
I,
think.
E
For
Chrome
on
build
is
like
get
CL
format
formats
your
commit
shows
highlights
the
diff
and
you
can
also
run
clang
format
to
and
get
the
reformatted
versions
and
submit
it,
and
we
can
also
figure
out
how
to
add
pre-commit
checks.
That
perhaps
does
that,
for
you,
there
is
an
option
to
override
the
form
and
turn
formatting
off
for
a
section,
and
if
there
is
a
strong
reason
to
do
that,
I
guess
we
can
say
hey.
This
is
how
you
disable
formatting
Auto
format.
For
a
section.
E
B
B
So
I
once
spent
like
a
few
minutes
on
this
PR,
so
talk
more
about
the
folder
structure.
I'll
make
the
change
according
to
what
we
discussed.
So
there
are
a
few
points.
I
want
to
ask
early
feedback.
The
first
one
is
a
like
in
this
library
I
think
given
were
trying
to
implement
the
trace,
comebacks
I,
wonder
if,
like
people
working
on
C
would
be
interested
in
having
this
or
we
should
just
use
a
pass
pass.
So
here
what
happened?
Trying
is
I,
try
to
support
mostly
and
say
pass
pass.
B
Another
thing
is
I
noticed
we
have
some
like
include
file
where
I
have
both
ApS
that
are
supposed
to
be
used
by
the
end
user
and
their
API
is
probably
only
used
by
the
SDK.
With
this
like
folder
structure,
two
weeks
at
the
API
folder
like
include
to
have
only
the
public
facing
a
official
thing
and
then
for
the
internal
API
is
that
can
be
used
by
the
like
some
other
folder
and
there's
an
API
package
or
in
the
istick
we're
really
about
that.
So.
C
C
E
Have
one
minor
comment
on
this
code
like
it's
from
today's
discussion
that
we
were
having
about
like
underscore
chip
being
used
in
interrupts,
and
it
seems
like
boys
X,
actually
reserves
that
for
physics,
standard
types
technically,
it's
going
to
be
a
violation
of
boys
X.
If
you
implement
your
own
status,
underscore
yeah
I
know
that
Android
also
defines
that
type.
E
B
Okay
and
regarding
namespace
I
have
this
question:
do
we
have
this
open
country
at
the
only
namespace,
or
we
have
like
sub
namespaces
I?
Think
I,
like
personally
I,
prefer
to
have
just
open
country
when
I
want
to
walk
with
magic
spaces.
I
don't
want
other
like
namespaces.
It's
not
a
huge
namespace
for.
C
B
Know
so,
please
put
your
comment.
This
is
just
like
personal
preference,
probably
well
just
moles,
so
if
you
have
more
friends
or
in
preference
of
your
like
style,
please
ask
them
most
here,
like
my
reason
is
because
when
I
nicely
like
the
I
speedy,
like
it's
a
hit
namespace
and
purifying
with
that.
C
D
B
C
B
This
so
I'll
finish,
this
folder
structure
are
based
on
our
discussion,
I'll
rebase,
this
PR
to
a
pawn
to
that
right,
folder
structure
and
did
not
expect
like
a
huge
number
of
comments
from
your
guys
and
most
likely
for
the
very
subjective
thing
we'll
do
a
bolt.
We
don't
have
a
hot
people
here,
so
we
have
five
wishes
good
number.
That
means
we
never
gone
like
two
like
two
years
and
tuned,
alright,
so
Ted,
please
also
have
on
the
morrow
keyhole,
we're
good
sure.
A
E
D
The
actual
compiler
than
the
standard
so
like
GCC
4.8,
it
is
what
we
require
for
open
tracing.
It
doesn't
support
all
of
C++
11,
but
practically
it's
like
enough
and
you
can
write
in
for
the
most
part
in
C++
11
minutes.
The
important
thing
is
to
put
it
in
the
CI
so
that,
if
you
break
it
and
you'll
know
right
right,
yes,
yeah,
it
sounds
reasonable
thing.
B
C
You
hey
Riley.
This
is
still
recording
I.