docs: clarify undefined behavior in pointer semantics example (fixes … #191
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…#182)
Add detailed comments explaining that the C code example contains undefined behavior when returning a pointer to a local variable. This example is intentionally shown to demonstrate how Go differs from C in memory management - Go handles this safely while C results in undefined behavior.
This resolves the misleading nature of the slide example and helps students understand the key differences between C and Go's approach to memory and pointers.