>my favorite keyword in C++ is "auto"
What type of person do you imagine?

>int main
ngmi
auto main() -> int {}

i dont use goyplusplus

>>105639909 (OP)
I can see the value when it comes to strange pointer return types, like nested pointers and function pointers

>>105639909 (OP)
people laugh at JS, but C++ is just as comically bad

I try not to imagine people.

>>105639971
Not even when you're fapping?

>>105639999
Okay but not C++ programmers. Yet.

>>105639938
Yuck!

>>105639956
i only use it for the autistic iterator return types from the stdlib.

>>105640114
>>105639956
There are lambda types that aren't nameable.

>>105639909 (OP)
>What type of person do you imagine?
i imagine someone that looks like sam bankman huffing and puffing, mouth breathing, sweaty and smells bad.

in Rust this is just "let"

>>105639999
linoleum tiles are the best for that

>>105640114
>she's still using iterators

>>105641269
what are you supposed to use?

>>105640114
Oh yeah, this.

>>105639909 (OP)
the same kind of retard who uses functors as his default way of declaring functions.

>>105639938
extremely based. fpbp.

>>105639965
Javascript's ducktyping and weird implicit casting rules are way worse than C++. They're both bad though, yeah.

>>105640132
they can be stored in a std::function though

>>105641279
ranges is a good start
what it gods name do you even NEED iterators for?

>>105641310
Yeah, but the type is still unnameable. You either have to use template or auto.

Gay retard javascript+python pajeet

>>105639999
What do you think all the monitors are for?
Checked.

>>105639909 (OP)
>What type of person do you imagine?
carbrain

>>105641311
It still looks bad compared withresult = vec & filter even & map ("2) & take 3

>>105639909 (OP)
Auto means a different thing for C (not in C23), but if those retards at the committee purposely change a keyword's semantic then why we still using _Atomic instead of "atomic"?

>>105641894
its not perfect, but still a massive improvement to iterators or god forbid "classic" C++
the shift towards more functional programming in C++ is highly erotic and retards lagging behind not using it will be obsolete
99% of what rust sells itself to be is already available in modern C++, you cannot convince me otherwise

>>105641999
>99% of what rust sells itself to be is already available in modern C++
lol

>>105641099
Rust should allow type omission in the function signature like C++ does, especially for the return type.

>>105642220
that sounds awful

>java(script) is... le bad!
>anyway here's c++69420 it's basically indistuinguishable from java(script) - and that's a good thing!

>>105641955
> change keyword meaning
They re-used auto because they didn’t know how to change the yacc or lex files.
But yeah, pretty embarrassing.
Also, auto itself is ass, you don’t know what type the fucking variable is half the time, like when you come back to the code. Other languages have the same problem, like Go.
Some of the more complex types I *never* knew the actual type, no idea what methods or public variables were.
Someone should make a ‘style’ ‘tidy’ or ‘fmt’ for C++ that replaces all the autos with their actual type.

>>105641894
> vector
Bwahahahaa..
You’re supposed to be using “generators” now!

Our services staff rewrote all their python (the only thing they’re allowed to touch) to use generators and made the code 10 times bigger.

>>105642661
>Our services staff rewrote all their python (the only thing they’re allowed to touch) to use generators
....huh? what does this have to do with C++?

>>105641955
You can't add new keywords willy-nilly as it will break existing code. In the case of auto, you already had a useless keyword right there to reuse.

>>105642615
Clangd can tell you the types.

>>105642787
Backwards compatibility sucks and at some point they will need to break the language, and it's ok.

>>105643093
Stealing basic words to replace with keywords is really disruptive. What if that word is the field name of widely used structure. The amount of code needing to be updated would be immense.

>>105639909 (OP)
C++ and Haskell are strangely enough very similar: they both came from an academic background where their designers were too busy adding new features to think whether it was a good choice for the language.

>>105639909 (OP)
#define var auto
#define let const auto

>>105643156
Who cares? the operator precedence order was never fixed and now you have much more code and year after year you will have more C code out there, not addressing these issues will cause a mayor pain in the future.

>>105643537
The C philosophy is don't fix anything and then say you can't fix it once at least one line of code depends on it. B was only used by the 2 people who made it and they were already complaining about not being able to fix strings or arrays in C because of "backwards compatibility."

>>105639971
Living life in peace?

>>105639909 (OP)
I use auto for function parameters too

>>105639909 (OP)
Myself. The only things I like more than auto are auto&& and constexpr auto.

>>105641894
last time I checked ranges add 3-5s to compilation you are better off using a third party library. In fact anything past c++17 adds ~4s

>>105644183
oh no 3-5s compilation time per unit that uses ranges
pro tip; if youre using ranges in every of your units you're probably doing something very very wrong

>>105639938
make it stop

>>105643270
Based.

>>105641894
>DUDE FUNCTIONAL PROGRAMMING
is this 2015

>std::
>std::
>std::
>std::
>std::
>std::
>std::

itt bad programmers whine about trivialities

>>105643093
Sutter is already on it.

>>105646190
using namespace std;
problem solved

>>105641894
Is there even a point in learning c++. 10 years ago i thought I had a good grasp of the stdl but every time c++ is brought up there is a new feature I had no clue existed

>>105646190
this is even uglies than rust

>>105646453
namespaces are gay my dude

>>105641310
And how do you think std::function is implemented? Do you think retarded template type deduction is more ergonomic than auto?

>>105646498
I honestly do not see the point unless you need it for work. The language seems intent on torturing itself into insanity and complete illegibility. Learn a language that is actually fun to write in while waiting for AI to replace handwritten code entirely.

>>105642787
c++ has some contextual keywords known as soft keywords elsewhere. auto auto could have been.

>>105639909 (OP)
I don’t assume at first. I wait and see how others expect him to act and determine his type that way.

>>105641126
Kek
Somebody share the image please.

>>105639909 (OP)
A professional C++ programmer. Usually they are quite intelligent, but it's a broad category.

>>105642615
You don't need to know the name of a type. It gives you no actionable information by itself.

>>105645412
its not per unit. Its the c++20 flag thats the problem because of ranges the headers all doubled or tripled which adds more time. Like I said its all feature flags beyond c++14 that add a couple seconds which makes using the std lib painful.

>>105641894
With operator overload and C++20 concepts you can have all that syntax candy you want and in the way you believe is better. Very handy for advent of code and personal projects.

>>105643270
Nice, but there is a template meta programming scenario where you need to write auto const because const auto doesn't work.

>>105639965
Skill issue, JS and C++ are the best languages.