Wolfgang Bumiller

Interesting setup. So I guess the question is how generic the solution should be. Simply doing it for bridge-connected devices, or adding a `lxc.network.sysctl.*` variable set, or adding a network-device...

Actually... just noticed there's already `lxc.network.script.{up,down}`.

After some discussions we think that this should emit a warning but is otherwise not really a "bug". Given C's definition of sequencing, the result types of assignments and, in...

Could still do it manually. But there's no rush there I think.

The inner workings of the qcvm warrant the label change to 'feature' ;p

This can probably use the same conditions on when to trigger as -Otailcalls would.

Might be good do note that when they are AST macros and you don't actually use a `{{{body}}}` in there, then the following will NOT work: ``` C macro for_stuff(n)...

Implementation wise we'd need to add copy-ctors to ast nodes. Which are also required for inlining. So I'm referencing #35 here.

Note: need a way to deal with immediates and variables properly for proper inlining support.

Definitely. We also need to solve the entity-field namespace problem. Currently you cannot use fieldpointers in `-std=gmqcc` because the fields themselves are not in the global scope. We should have...