coders-school / memory-management Goto Github PK

On brunch resource in memory-management/.github/scripts/check.sh one testcase assumes that user didn't modify the file before pushing to the server:
pattern ${FILE} "Looking for the allocation place" "main \(resourceD.cpp:30\)"

Fixed in PR: #104 (comment)
Commit: 9984136

In Semantyka przenoszenia: 0x0E Copy elision video 5:02min you add word no. 24, this is a second time in this module, I don't know in which video appear firs time, but I have already this word in my notes.

In homework's readme:

https://github.com/coders-school/memory-management/tree/shared_ptr/homework/shared_ptr

I found outdated links:
"Pre-work
Read the presentation about move semantics and std::forward
Read the variadic template part of this presentation
It will be useful for a post-work ;)"

Wskaźniki inteligentne
0x0C ResourceFactory
https://user-images.githubusercontent.com/77102726/134931566-f4ec50eb-5c0c-4181-a307-7ad1b77f1d65.png

In Semantyka przenoszenia: 0x03 l-value, r-value video 2:22min you add word no. 16, this is a second time in this module, I don't know in which video appear firs time, but I have already this word in my notes.

Deleted copy constructor and copy assingnment operator incorrectly detected as not implemented.

In 0x03 unique_ptr video 4:12min you add word no. 9, this is a second time in this module, I don't know in which video appear firs time, but I have already this word in my notes

In file module2/smart_pointers_best_practices.md

"order of evaluation" A1, A2, B1, B2, C3, C3

there is no C-element

#27 PR

Since October 2022 there is a new version of the file-existence-action. In .github/workflows/main.yml the line
uses: andstor/file-existence-action@v1 should be changed to uses: andstor/file-existence-action@v2

Check official repository for reference:
https://github.com/andstor/file-existence-action

In Semantyka przenoszenia: 0x0A std::move video 2:33min you add word no. 1, this is a second time in this module, I don't know in which video appear firs time, but I have already this word in my notes.

Breaking cycle - solution
Use std::weak_ptr in one direction
`
#include
struct Node {
std::shared_ptr child;
std::weak_ptr parent;
};

int main () {
auto root = std::shared_ptr(new Node);
auto child = std::shared_ptr(new Node);
root->child = child;
child->parent = root;
}`

Problem with naming convention. Same names as node members in Node class, and as main shared_ptr objects.

Outro test. Question from memory#2.
I think answers "in line 13 uptr is already nullptr" and "in line 12 uptr is already nullptr" are ambiguous, because in line 13 uptr is still nullptr. The applicant doesn's know if You mean it's first time nullptr or it's still nullptr.