jekky
jekky
you're right, this function seems to be calling itself, that's why: `this.OnUpdate(timeDelta, stateContext, scriptInterface);` needs to be replaced with `super.OnUpdate(timeDelta, stateContext, scriptInterface);` this looks like an issue with the decompiler,...
thanks for the report, I'll change this issue to track a decompiler bug
I think declarations could be checked, the line here is responsible for checking declarations without an initializer: https://github.com/jac3km4/redscript/blob/master/compiler/src/typechecker.rs#L111 it could look like this: ```rs (Some(type_name), None) => { let resolved...
I've thought about this, and there's still a problem of fields that have an abstract type but exist on a non-abstract type, they'd need to be handled too and that...
I guess the simplest thing to do would be to disallow having abstract structs as fields at all
good catch, this seems to be an issue with `cb` and `native` functions - the way they're matched (using function signatures) in this case ignores the function parameter types which...
I've just stumbled upon this as well... It seems that with the new API the example should be rewritten like this: ``` javascript @asyncConnect([{ key: 'lunch', promise: (params, helpers) =>...
the typedefs can replaced with c++-style using type aliases
You can use namespaces on the latest version, I've also changed it to output rva in the output headers by default
should be fixed with eea9a2aa56a498d3f047ae8c56aca2124530cdde