@programminginc - страница 1401

Dima

std::allocator

Ludovic 'Archivist'

It is generally linked optionally

Just like std::filesystem

Dima

std::*

Ludovic 'Archivist'

std::allocator

This also have a very nice use, mainly for allocating in files or other structures

BinaryByter

std::allocator

allocztor is the best thing that happened to cpp

BinaryByter

allocztor is the best thing that happened to cpp

amongst*

Ludovic 'Archivist'

This also have a very nice use, mainly for allocating in files or other structures

Or just for implementation of a garbage collector

Ariana

@rose you know anything about c or c++ or u r just here for welcoming noobs

XD

Ariana

this is the best msg i’ve read in my life

Ariana

Rose is actually a neural network

Ariana

Its currently in training phase, just in case it spews nonsense

Ariana

would be ready soon

BinaryByter

We dont train it in indian msgs

Dima

trained by indian messages lmao!

Dima

the most retarded neural network ever

Anonymous

/

klimi

@rose you know anything about c or c++ or u r just here for welcoming noobs

Thats a stupid question

mark

Thats a stupid question

😂😂😂😂

mark

Same as the person who said it

klimi

😂😂😂😂

That's a stupid reaction

psy4

He is actually not exactly wrong

Would you like to hear more ? Then, I'd go ahead and say recent changes to the STL are the worst parts of modern C++. For example std::regex supports 6 distinct syntaxes, the PRNG stuff is massively over-engineered, the "extensions for parallelism" add complexity without giving enough knobs for any real perf improvement. Meanwhile there's gaping holes like UTF-8 support. It's a sad sad state. 😢

psy4

mem_func_ptr aside

My main issue here is combining multiple libraries each using its own abstractions. For example, since the standard library does not have a Matrix class suitable for numerical applications (or maybe it does today...) using multiple libraries each with its own Matrix class is difficult. Multiple libraries are needed since one library may not contain all numerical algorithms one may require for a given app.

Ludovic 'Archivist'

Would you like to hear more ? Then, I'd go ahead and say recent changes to the STL are the worst parts of modern C++. For example std::regex supports 6 distinct syntaxes, the PRNG stuff is massively over-engineered, the "extensions for parallelism" add complexity without giving enough knobs for any real perf improvement. Meanwhile there's gaping holes like UTF-8 support. It's a sad sad state. 😢

But all of these are never mandatory and are separated

Ludovic 'Archivist'

Also about 98% of the bloat is blown away at link time

Ludovic 'Archivist'

Would you like to hear more ? Then, I'd go ahead and say recent changes to the STL are the worst parts of modern C++. For example std::regex supports 6 distinct syntaxes, the PRNG stuff is massively over-engineered, the "extensions for parallelism" add complexity without giving enough knobs for any real perf improvement. Meanwhile there's gaping holes like UTF-8 support. It's a sad sad state. 😢

But yeah, utf support is a serious issue

Ludovic 'Archivist'

I cannot shrug that one off

psy4

But all of these are never mandatory and are separated

The problem is there's no easy to use sensible defaults, just a confusing bunch of options with a bunch of apparently easy but subtely wrong ways to use it. Having the power is useful, for instance, I would just like a rand() as a sane option(or better a randrange()) which actually works instead of nitpicking stuffs.

Ludovic 'Archivist'

The problem is there's no easy to use sensible defaults, just a confusing bunch of options with a bunch of apparently easy but subtely wrong ways to use it. Having the power is useful, for instance, I would just like a rand() as a sane option(or better a randrange()) which actually works instead of nitpicking stuffs.

Well, rand never worked even in C

Ludovic 'Archivist'

int rand() {return 4;} is a valid implementation

psy4

forget rand let's say stdlib lacking common operations like proper database connections or say, efficient JSON parsing

Ludovic 'Archivist'

forget rand let's say stdlib lacking common operations like proper database connections or say, efficient JSON parsing

Well, this is imho pretty normal for the database part, I agree for the JSON part tho but add that and people yell it is bloat

Ludovic 'Archivist'

Well, this is imho pretty normal for the database part, I agree for the JSON part tho but add that and people yell it is bloat

All the while there are well balanced header only C++ libs for JSON

psy4

Sometimes I wonder, C++ shouldn't have had a standard lib at all

Ludovic 'Archivist'

Sometimes I wonder, C++ shouldn't have had a standard lib at all

It should just have the freestanding implementation imho

psy4

yeah ,for me basic leaf modules would suffice

Ludovic 'Archivist'

yeah ,for me basic leaf modules would suffice

I think the worst feature of the stdlib is still the locale faucets

psy4

I think the worst feature of the stdlib is still the locale faucets

yeah, I'd get rid of those and few more garbage ASAP. At last, we experienced devs or people that need domain specific features would be using our own specialised libraries anyways. 🥂

Ludovic 'Archivist'

yeah, I'd get rid of those and few more garbage ASAP. At last, we experienced devs or people that need domain specific features would be using our own specialised libraries anyways. 🥂

https://github.com/clinlfoundation/FEL

Ludovic 'Archivist'

It is still very WIPy

psy4

yeah I saw this one

psy4

it's still pretty barebones for me

Ludovic 'Archivist'

Takes time to make shit

Ludovic 'Archivist'