Summary:[Folly] `s/MAX_STATIC_CONSTRUCTOR_PRIORITY/FOLLY_STATIC_CTOR_PRIORITY_MAX/g`.
Namespace it with a `FOLLY_` prefix - when Folly introduces its own symbols, it is best when they are namespaced.
And stick `_MAX` at the end. Reads a bit more hierarchically to me that way.
Reviewed By: andriigrynenko
Differential Revision:
D3095964
fb-gh-sync-id:
4ac8c00c03c8bd146fad9be96ce3849830504d96
fbshipit-source-id:
4ac8c00c03c8bd146fad9be96ce3849830504d96
#endif
#if defined(__APPLE__) || defined(_MSC_VER)
-#define MAX_STATIC_CONSTRUCTOR_PRIORITY
+#define FOLLY_STATIC_CTOR_PRIORITY_MAX
#else
// 101 is the highest priority allowed by the init_priority attribute.
// This priority is already used by JEMalloc and other memory allocators so
// we will take the next one.
-#define MAX_STATIC_CONSTRUCTOR_PRIORITY __attribute__ ((__init_priority__(102)))
+#define FOLLY_STATIC_CTOR_PRIORITY_MAX __attribute__((__init_priority__(102)))
#endif
#endif // FOLLY_PORTABILITY_H_
return threadEntry->elements[id];
}
-MAX_STATIC_CONSTRUCTOR_PRIORITY
+FOLLY_STATIC_CTOR_PRIORITY_MAX
PthreadKeyUnregister PthreadKeyUnregister::instance_;
}}