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
One thought I had was to maybe replace the type specific traces (TRACE_TENSOR and so on) by inline functions so the normal c typechecker can act upon these, but this can also be an issue for later (function type errors are more readable than macro errors for most people :D).
I would only replace macros which have no variadic arguments, since I don't know if handling of variadic arguments in functions is portable.
One thought I had was to maybe replace the type specific traces (
TRACE_TENSOR
and so on) by inline functions so the normal c typechecker can act upon these, but this can also be an issue for later (function type errors are more readable than macro errors for most people :D).I would only replace macros which have no variadic arguments, since I don't know if handling of variadic arguments in functions is portable.
Originally posted by @nopeslide in #49 (comment)
The text was updated successfully, but these errors were encountered: