You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see containers.h being #included in almost every module, which is probably the point, but is this just a specific choice: "include it everywhere, if we ever need it it'll be in scope and if we don't the compiler will just ignore it"? Or is this an oversight and is it better to limit the amount of CPP pragmas and inclusion of C headers?
Asking in case someone (me?) might want to clean it up, or that this is intentional and should stay this way.
The text was updated successfully, but these errors were encountered:
I see
containers.h
being#include
d in almost every module, which is probably the point, but is this just a specific choice: "include it everywhere, if we ever need it it'll be in scope and if we don't the compiler will just ignore it"? Or is this an oversight and is it better to limit the amount of CPP pragmas and inclusion of C headers?Asking in case someone (me?) might want to clean it up, or that this is intentional and should stay this way.
The text was updated successfully, but these errors were encountered: