-
```
When compiling using the latest gcc, the compiler assertion used by LOG_EVERY_N
generates an unused typedef warning:
warning: typedef ‘INVALID_REQUESTED_LOG_SEVERITY’ locally defin…
-
```
When compiling using the latest gcc, the compiler assertion used by LOG_EVERY_N
generates an unused typedef warning:
warning: typedef ‘INVALID_REQUESTED_LOG_SEVERITY’ locally defin…
-
Currently, we use three macros in [`ASSERT`](https://github.com/shogun-toolbox/shogun/blob/fa5a9b683e980d0a9b637b4ffbaca59d5917cf20/src/shogun/io/SGIO.h#L190), [`REQUIRE`](https://github.com/shogun-to…
-
## Problem
Add support for user-defined macros that can concisely represent larger authorization logic statements or collections of rules. The macro syntax should also support arguments. Here is a mo…
aferr updated
2 years ago
-
```
When compiling using the latest gcc, the compiler assertion used by LOG_EVERY_N
generates an unused typedef warning:
warning: typedef ‘INVALID_REQUESTED_LOG_SEVERITY’ locally defin…
-
```
When compiling using the latest gcc, the compiler assertion used by LOG_EVERY_N
generates an unused typedef warning:
warning: typedef ‘INVALID_REQUESTED_LOG_SEVERITY’ locally defin…
-
```
When compiling using the latest gcc, the compiler assertion used by LOG_EVERY_N
generates an unused typedef warning:
warning: typedef ‘INVALID_REQUESTED_LOG_SEVERITY’ locally defin…
-
```
When compiling using the latest gcc, the compiler assertion used by LOG_EVERY_N
generates an unused typedef warning:
warning: typedef ‘INVALID_REQUESTED_LOG_SEVERITY’ locally defin…
-
```
When compiling using the latest gcc, the compiler assertion used by LOG_EVERY_N
generates an unused typedef warning:
warning: typedef ‘INVALID_REQUESTED_LOG_SEVERITY’ locally defin…
-
```
When compiling using the latest gcc, the compiler assertion used by LOG_EVERY_N
generates an unused typedef warning:
warning: typedef ‘INVALID_REQUESTED_LOG_SEVERITY’ locally defin…