I tried to write out some code for Project #3 until I saw that the header was posted (yay!) and then switched gears to start understanding the header file and structure the project the way the header file suggested.
The syntax of C++ still isn't intuitive to me, so I've been spending a lot of time just staring at the header file and wondering why the signatures were written the way they were and how I'm supposed to actually implement the code. I have a conceptual understanding of what should be going on and I know how to write it in python, but I'm stumped when it comes to C++.
I'll definitely continue to work on the project and I'll try to ask my classmates for help. I feel nervous posting to Ed since everyone can see who posted, but I've found a lot of the posts helpful. Once I feel more comfortable with more of my classmates, I might start posting as well.
I think it paired pretty well with the previous paper (Liskov Substitution Principle). I feel like the Liskov Substitution Principle helps when deciding when to make subclasses v. sibling classes, whereas the Integration Segregation Principle helps to figure out what the class should be a subclass of (ie. where to put it in the hierarchy). So they're pretty similar (from my perspective).
It seems like the main issue with heap-allocated arrays is how they need to be deallocated properly (it's easy to lose track of where they are) and how they can be copied (which can lead to memory leaks). I learned that std::vector has an option to initialize all of the entries to a certain value upon construction. I felt comfortable with DigitsIterator (the first exercise that I felt really comfortable doing! yay!).
I went to Holi with my friends! I was really, really stressed earlier in the day, but my friends and the event helped me feel more happy and confident to finish my work afterwards.
Not