serenity
serenity copied to clipboard
Kernel: Refactor Filesystem-Mounts hierarchy design
Fixes #11283.
Shouldn't there be include guards to prevent include loops?
Shouldn't there be include guards to prevent include loops?
There's the #pragma once statement. Still headerA.h can include headerB.h and then headerB.h can include headerA.h, which will lead to a compile error if there are class definitions in both headers that use each other.
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions!
This is not stale.