Yep, but one is not aware how unreadable a piece of code can get if template metaprogramming gets outof hands

That's why we comment our code.

That's why we comment our code.

Trust me, comments don't make template metaprogramming code that easier to read

That's why we comment our code.

What if code can speak itself?

What if code can speak itself?

this imo. comments should describe why something is happening, not what is happening

this imo. comments should describe why something is happening, not what is happening

In fact, code should express the intentions itself

Comments get outdated quickly. Code is what it is

I mean but if I can use 1 header file, 30 lines of templated code, to replace 5 files with thousands of lines of code, I am going to do that.

Comments get outdated sure, but so does code.

I mean but if I can use 1 header file, 30 lines of templated code, to replace 5 files with thousands of lines of code, I am going to do that.

Good luck

I mean I already did

Great

But it took weeks to do it. And whenever I asked the internet on how to accomplish what I wanted. They seem to know the answers. Hence why I asked that question, because I want to get on their level of knowledge on templates.

But I bought a really good book on them, so this conversation isn't necessary anymore.

okey

I love this way: https://suckless.org/philosophy/

#cppbook

ah :)

You can retrieve these notes by using /get notename, or #notename

/notename

You can retrieve these notes by using /get notename, or #notename

Like this?

/get cppbook

like this

/notename

🤦‍♂

🤦‍♂

Ok

/get gcc9

#cpp

#ide

#best-book

You don't master templates, trust me, you'll be safer away from them

Wut? Templates ARE safety. It is a 100% compile time safe language, templates are the only part of C++ that you can always check at compile time

templates add a lot of code bloat though

c++ adds a lot of code bloat though

depending on how extensiely you use them

yep

templates add a lot of code bloat though

doesn't make them less safe tho

wrong

code bloat is a kind of unsafety

more bloat more options to have vulnerabilities in the bload

kind of a bloating bloatware failure

more bloat more options to have vulnerabilities in the bload

> templates > vulnerabiliities uh wtf

like that argument would apply if there was extra code involved, there isn't

like that argument would apply if there was extra code involved, there isn't

templates without extra code?

also they're too straightforward to mess them up (unless abusing them)

right, so you just spit on the screen and the compielr remembers that you wanted a template at that position

templates without extra code?

it's all templating of existing code

right, so you just spit on the screen and the compielr remembers that you wanted a template at that position

?

?

Stupid idea, right? So why claim that there is no extra code involved in templates

templates add a lot of code bloat though

Lack of experience detected! Templates is a good way to reduce bloat, esp binary bloat. CC: @QNeko

Lack of experience detected! Templates is a good way to reduce bloat, esp binary bloat. CC: @QNeko

i said depending on how you use them

Lack of brain detected!

Lack of brain detected!

^ I agree

Stupid idea, right? So why claim that there is no extra code involved in templates

no it's simply templating existing code

^ I agree

you agree with and will "^" everything he and Wim say. we get it

no need

you agree with and will "^" everything he and Wim say. we get it

No

No

yes

its just that I agree with him

is agreeing with someone forbidden?

well... its forbidden when i'M agreeing with you 😂

its just that I agree with him

on 100% of occassions

he's just having a hard time finding anything anyone would agree on with you...

i said depending on how you use them

"depending on how you use them" is true for a lot features.

he's just having a hard time finding anything anyone would agree on with you...

i'm tryharding the searching 😂

"depending on how you use them" is true for a lot features.

this depending on how you use them makes templates potentially dangerous

Sure they are nice

i'm tryharding the searching 😂

easy. just build a time-machine and go back to before you met these two. then come back here without having met them

templates add a lot of code bloat though

Sure, better have 122 different types of vectors for each type and allocators you use them with so that you have less code bloat

Sure, better have 122 different types of vectors for each type and allocators you use them with so that you have less code bloat

safer lmao

Sure, better have 122 different types of vectors for each type and allocators you use them with so that you have less code bloat

easy. just build a time-machine and go back to before you met these two. then come back here without having met them

Lets recap who i'd be then: - unpopular in school - having no clue on how to write asm - believing that RSA is secure (lol) - believing in secure crypto - C++ fanboy lets not build that time machine 😂

Sure, better have 122 different types of vectors for each type and allocators you use them with so that you have less code bloat

thats not what I said

safer lmao

Definitely, you can read the definition faster, there are just lots of them

these two retards again.. come on

no wait, three.

why? because maxi is at least mentally capable of looking beyond his nose and gets c++ is not the ideal solution to everything? so you'd rather have him be stupid again?

thats not what I said

Well you said it reduce code bloat to remove templates

why? because maxi is at least mentally capable of looking beyond his nose and gets c++ is not the ideal solution to everything? so you'd rather have him be stupid again?

yeah well he's now the other extreme

Well you said it reduce code bloat to remove templates

Well, you said the converse proposition

not better

Well you said it reduce code bloat to remove templates

why don't we have a look at libraries that use templates more than just vector?