I saw the problem is happening on *(ptr+i) = *(ptr+len-1-i);

Getting write access voilation

Check for boundaries

How bro?

Using the magic of gdb

You'd have to call it anyway. It's UB otherwise

Can you guide?

There are three types of memory in C++: The Stack, Static Memory, and the Heap

Then you'd know everything is either 0 or nullptr

Then you'd know everything is either 0 or nullptr

Wanna I break your brain? There's no "stack memory" in C++ And no heap

Yeah we know standard was made by ancient reptiloids who defy human logic

Yeah we know standard was made by ancient reptiloids who defy human logic

Or whatever debugger you got

You mean that the object shall be zero filled?

Wanna I break your brain? There's no "stack memory" in C++ And no heap

Could you please elaborate?

So Stack and Heap are just the most common concepts for implementation?

Yes

In Programming language, how much the importance of math?

Was wondering can we edit the iostream file to change name "std" to something else?

;________;

Do an alias

Oh wait how XD

What's wrong with std

namespace foo = std;

Was wondering can we edit the iostream file to change name "std" to something else?

Why would you do that anyway?

Is there any kotlin telegram group to ask a question related to kotlin?

@en_it_chats

No kotlin there!

Hi can anyone send me kernel device driver handwritten notes

Try to ask in Java / Scala groups

ban incoming

Hmm, watching this talk, stumbled upon this code, do anyone know how these overloads (with const & and && at the end) named so I can google them? (timecode) https://www.youtube.com/watch?v=xTdeZ4MxbKo&t=2396 std::string std::stringbuf::str() const &; std::string std::stringbuf::str() &&;

Hmm, watching this talk, stumbled upon this code, do anyone know how these overloads (with const & and && at the end) named so I can google them? (timecode) https://www.youtube.com/watch?v=xTdeZ4MxbKo&t=2396 std::string std::stringbuf::str() const &; std::string std::stringbuf::str() &&;

Yeah they overload the methods for reference types so you can overload a method if it's called on R or L value for example

why we do that?! why an instance of class have diffrent behaviors on rvalues and lvalures? I cant find an usefull example that force us to use it?

the biggest usage is to prevent modifiers from being run on temporaries

the biggest usage is to prevent modifiers from being run on temporaries

Hm, you mean we can have a function overloads that run on let's say only on & or const& then it will be a compile error if it will be called on a temporary?

yep. imagine std::vector::clear() & { /* ... */ }

Interesting

yep. imagine std::vector::clear() & { /* ... */ }

oops , I got it :D thx.

another (probably better) example. avoid deep-copy for temporary. @gameraccoon Foo Foo::sorted() && { sort(data.begin(), data.end()); return *this; } Foo Foo::sorted() const & { Foo ret(*this); sort(ret.data.begin(), ret.data.end()); return ret; }

another (probably better) example. avoid deep-copy for temporary. @gameraccoon Foo Foo::sorted() && { sort(data.begin(), data.end()); return *this; } Foo Foo::sorted() const & { Foo ret(*this); sort(ret.data.begin(), ret.data.end()); return ret; }

Oh, also interesting by the way, should it be std::move(*this) in the first variant?

why we do that?! why an instance of class have diffrent behaviors on rvalues and lvalures? I cant find an usefull example that force us to use it?