stack/intro: Lab 8 - Stiva

[george-cosma]

Prerequisite Checklist

• Read the contribution guidelines regarding submitting new changes to the project;
• Tested your changes against relevant architectures and platforms;
• Updated relevant documentation (if needed).

Description of changes

Initial draft done, can be reviewed

[george-cosma]

Am sa dau fix la erori cam vineri-ish, sau pe weekend

[teodutu]

The content is mostly fine. Most of my inline suggestions apply to all code files. In addition

1. Fix the github action test failures [1]. For the spellcheck false positives, you'll have to add the missing words to these wordlists here [2] as a separate PR.
2. Squash your commits to a single one named something like stack/stack: Add lab exercises, guides and reading + a description and signature.

[1] https://github.com/cs-pub-ro/hardware-software-interface/pull/22/checks
[2] https://github.com/cs-pub-ro/hardware-software-interface/actions/runs/8829121620/job/24239469518?pr=22

[teodutu]

Remake this image as .svg and rename it to process-address-space.svg. We only use snake_case for source code file names.

[github-actions]

Published at https://cs-pub-ro.github.io/hardware-software-interface/22/

[github-actions]

Published at https://cs-pub-ro.github.io/hardware-software-interface/22/

[george-cosma]

Don't know how to fix spellcheck. Otherwise done 👍

[teodutu]

I made inline comments with what needs changing. To fix spellcheck, add the false positives to these wordlists [1] and keep them sorted and avoid duplicates using sort -u -o <file-name> <file-name>.

[1] https://github.com/open-education-hub/actions/tree/main/spellcheck/config

[teodutu]

Split this file into the following files and group the exercises and demos around them (where possible) so they form subchapters:

• introduction.md (intro + stack data structure)
• stack-operations.md
• stack-addressing.md

[george-cosma]

The content is quite short, I think splitting up the concepts will just end up with more confused students. Teach them what they need to know, then let them practice. Splitting it off so atomically is just not worth it imho

[teodutu]

Ok then remove the "Introduction" subchapter in config.yaml and make the links in the tasks refer to specific sections in the reading material (using #, such as .../README.md#stack-operations).