calixteman

A possibility is to have an Option< Result > for dynamic field and so let people handle errors like they want. Wdyt ?

[IBM935.so.zip](https://github.com/m4b/goblin/files/4850057/IBM935.so.zip) The debug file comes from Fedora's glibc.

If you run rca with `-p foo.py --metrics` then you'll get metrics for classes, functions, nested functions and so on. So what you're asking for is almost the hierarchy without...

The trait could be more general: - just add a result and do whatever you want with it: merge with prev results, dump it, write it in a file, ......

The default conf keep-alive is: https://github.com/actix/actix-web/blob/master/src/server.rs#L89

With `x => x` there is only one param: https://github.com/tree-sitter/tree-sitter-javascript/blob/master/grammar.js#L678 and so we should get `parameter` instead of `parameters`: https://github.com/mozilla/rust-code-analysis/blob/master/src/metrics/fn_args.rs#L75-L112 To avoid such inconsistency, we should likely add a `s`...

Maybe having something like ```rust DemangleOption { rust: u64, msvc: u64, ... } ``` and some constants we could use with "or" operator would be enough.

Yeah if you dump the ast for this code: ``` `- {translation_unit:228} from (1, 1) to (6, 1) |- {preproc_include:229} from (1, 1) to (3, 1) | |- {#include:2} from...

Macros are really a big big pain... and can give some very messy asts. I was wondering if it would be possible to combine extras and external: - a macro...

An other idea I had: - preprocess the file to replace macros name by "$ * len(name)": - the preprocessing could be made with a parser which gets valid identifiers...