AuroraSupport/AuroraRuntime
2
1
Fork 0
Code Issues 27 Pull Requests Releases Wiki Activity

[*] im not being bitched around by clang anymore. fuck you

Browse Source
This commit is contained in:
Reece Wilson 2024-01-06 03:25:56 +00:00
parent 3c7eff396f
commit 4a4f4e9608
2 changed files with 19 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Include/Aurora/IO/Loop/Loop.hpp
View File

@ -24,7 +24,7 @@ namespace Aurora::IO::Loop
// optTimeoutMS = 1 | 1ms
AUKN_SYM bool WaitMultipleLoopSources(const AuList<AuSPtr<Loop::ILoopSource>> &lsList,
AuList<AuSPtr<Loop::ILoopSource>> &signaled,
bool bAny = true,
bool bAny = { true },
AuOptional<AuUInt32> optTimeoutMS = {});
static const AuUInt64 kWaitMultipleFlagAny = 1 << 0;
@ -33,7 +33,7 @@ namespace Aurora::IO::Loop
AUKN_SYM bool WaitMultipleLoopSourcesEx(const AuList<AuSPtr<Loop::ILoopSource>> &lsList,
AuList<AuSPtr<Loop::ILoopSource>> &signaled,
AuUInt64 uFlags = kWaitMultipleFlagAny,
AuUInt64 uFlags = { kWaitMultipleFlagAny },
AuOptional<AuUInt32> optTimeoutMS = {});
struct ILSSemaphore : virtual ILoopSource

17
Include/Aurora/Runtime.hpp
View File

@ -31,6 +31,23 @@
#endif
#include <uuid.h>
#if defined(AURORA_COMPILER_CLANG) || defined(AURORA_COMPILER_GCC)
// Fuck you Clang, you can suck my dick
// Yes, this will infest every project that includes AuroraRuntime.hpp.
// No, I dont care.
// Stop adding retarded screeching warnings over stylistic choices.
// This use-case goes beyond the clangIgnore fields of our build scripts.
// We shouldn't need or desire viral/include-recursive warning dismissal, yet here we are.
#pragma clang diagnostic ignored "-Wbraced-scalar-init"
// Consider: VIS void MyFunc(int a, int b = { 2 }, int c = { 3 })
// Consider: how much legacy C code used { NULL [, ...] } as a generic initializer of member pointers *and integers*
// Why the hell should this resort in screeching from every translation unit parsing the runtimes' API?
// ...why should I care *NOT TO* sneak in additional universal warning ignores when this is the absolute state of clang and gcc?
// ...i'm not infecting my (and others') buildchain[s] with retarded piss, nor am i going to give a shit about your obsession with pragmatic build warnings (-Wall -pedantic, etc), in the face of these dog-shit compilers.
// Who thought Type value = { 0 } should be a fucking error in boomer corps, and a warning in the best case scenario? who?
#endif
#define AUKN_SHARED_API(name, type, ...) AU_SHARED_API_EX(AUKN_SYM, name, type, ## __VA_ARGS__)
#define AUKN_SHARED_SOO(name, type, size, ...) AUKN_SHARED_API(name, type, ## __VA_ARGS__) AUROXTL_INTERFACE_SOO_HDR_EX(AUKN_SYM, name, type, size)
#define AUKN_SHARED_SOO_NC(name, type, size, ...) AUKN_SHARED_API(name, type, ## __VA_ARGS__) AUROXTL_INTERFACE_SOO_HDR_EX_NC(AUKN_SYM, name, type, size)