Elliot Chance

You will need to modify the regex that handles the parsing of a unary operator: https://github.com/elliotchance/c2go/blob/master/ast/unary_operator.go#L15-L36 You must use your panic as a test case, like this: https://github.com/elliotchance/c2go/blob/master/ast/unary_operator_test.go#L39-L48 The panic...

This error happens when it cannot understand a line from the clang AST output. See here for an example on how to fix: https://github.com/elliotchance/c2go/pull/770

This is because we haven't done very much testing against windows and you have discovered a new AST node type that c2go doesn't know how to handle. Here is an...

Thanks for finding this bug. It is quite easy to fix if you would like to have a go. See this: https://github.com/elliotchance/c2go/issues/794

That's impressive you got it to work!

Thanks @jcburley !

This is because c2go does not understand one of the output lines from the clang AST. It can be fixed by adding a test case to `var_decl_test.go`, just like this:...

Ah yes, this has popped up once before. It's because it has to be wrapped (a little ugly) in a closure, like: ```go return func () int { counter +=...

Yes, as I said the mechanism to determine if the expression can remain inline or must be translated is not working for that return expression.

I believe @Konstantin8105 worked mostly on getting the `typedef` and `struct` parts working c2go, so I don't immediately know why the panic is happening. if you are able to debug...