David Anderson
David Anderson
I'm open to allowing one-liners like this, as long as there is only a getter OR setter (not both), *and* the function body is at most one statement. But regardless...
It's definitely within a compiler's job description to prevent unwanted practices. Your use case is a classic example of where automatic code generation is much more preferable. Have a script...
"Not I," said the cow.
If you'd like to submit PR with a working prototype I'd be happy to review it. The macros cannot be completely obsoleted but I think there's a strong chance the...
Very cool, thanks for looking into this. Feel free to share patches and I can take a look. Note that we have to stay ABI and API compatible but new...
I can't really think of a good reason to say "no" to this. I'm guessing enum structs should have it too.
Two short comments. I don't have a strong opinion on unstructured memory access. However, it should be a last resort. It's inherently less maintainable and more susceptible to breakage. Having...
@Th3-822 calling `m_requestedFrames.clear()` should be fine. Either way, your fix looks good.
Enums have very weird interactions with arrays. Try removing the tag (eg _:X_AXIS). Or, use enum structs.