Evan Shaw

The problem with using straight `u32` for the Rust type is that if we do this: ```rust fn rust_fn(ch: u32) {} #[cxx::bridge] pub mod ffi { extern "Rust" { fn...

So just to be clear, would you expect to be able to write: ```rust fn rust_fn(ch: u32) {} #[cxx::bridge] pub mod ffi { extern "Rust" { fn rust_fn(ch: char32_t); }...

After trying to implement this, I've run into a couple challenges: First, it doesn't work when a member variable has a deleted default constructor, such as `rust::Box`. Maybe we can...

After exploring my options a bit more I think in my case it makes more sense to use a handwritten `ExternType` impl as [described here](https://cxx.rs/extern-c++.html#integrating-with-bindgen-generated-or-handwritten-unsafe-bindings). I'll leave this issue open...

I'm still very interested in seeing this happen.

While not ideal, this seems like something that can be easily fixed through ESLint and the `eslint-fix` plugin, either using the `indent` rule or with `eslint-plugin-prettier`. Were you running the...

It looks like this can happen if the React types package (`@types/react`) is not installed when the migration runs. In this case, `ts-migrate` cannot tell that `setState` comes from the...

Thanks, I think I have an idea of what could cause this issue. If you specify `useDefineForClassFields` in `tsconfig.json`, then the compiler will define each property using `Object.defineProperty`, which initializes...

I think the problem is that you're not specifying a directory. For example, if you want to run `ts-migrate` in the current directory, you could try: ``` npx ts-migrate --...

I can see the use case here, though it does present some challenges in maintaining this project. I don't plan to work on this, but I'll jot down some thoughts...