Make C++ function overloading less dependent on source ordering

It would be nice to be able to rename the rust-side name for overloaded methods (methods and constructors) based on their signature by passing in some kind of mapping file to bindgen. Without this, there's no guarantee that the function names will be stable (e.g. if upstream adds another constructor/overload).

If there's an easy way to parse rust-like syntax (e.g. via the macro mechanism, but dynamically?), then maybe a mapping file could look something like:

rename SkPaint {
    SkPaint() -> Self => new;
    SkPaint(*const root::SkPaint) -> Self => new_copy;
    someOverloadedMethod(i32) => some_overloaded_i32;
    someOverloadedMethod(f32) => some_overloaded_f32;
    // remove this method from the output entirely, overloaded or otherwise (maybe?)
    anotherMethod(i32) => None;
}

someone could later expand upon that to allow you to reorder arguments or manually specify which method to call to implement Clone or Copy traits.