Brian Silverman

I got pretty far assuming that none of the generated C++ code depends on the symbols emitted by the procedural macro, before doing something with Box that requires it. Add...

[Rust] Proposal for non-owning FlatBufferBuilder API

3

I'd like to use a FlatBufferBuilder directly into an externally-allocated buffer from Rust. Some context: I'm looking to implement the equivalent of [this C++ API](https://github.com/frc971/971-Robot-Code/blob/aa3b08658485f4482759d253fea93a79afebb8ae/aos/events/event_loop.h#L344). It's an interface to a...

crossbeam-channel uses pure userspace spinlocks, which perform very poorly in some situations

10

crossbeam-channel appears to use pure spinlocks (which never block in the kernel), from userspace, which is a bad idea. Looking at the behavior with `strace`, it appears to be `sched_yield`ing...

I'm pretty sure that the current wrapper for `X::is_global` for this type is not callable without undefined behavior: ```c++ class X; X *global_x = nullptr; class X { X() {...

`test_issue_1089` fails locally for me

1

Tests fail for me like this on current main (cdebaee6434b90d9711278ca1493519274f232be), despite passing in CI: ``` thread 'integration_test::test_issue_1089' panicked at '"a__(anonymous_namespace)__ac__bj" is not a valid Ident', /home/brian/.cargo/registry/src/github.com-1ecc6299db9ec823/proc-macro2-1.0.37/src/fallback.rs:701:9 stack backtrace: 0: rust_begin_unwind...

Fix and test constructor wrappers in multiple include_cpps

4

The naming convention that just used the C++ function name directly doesn't work with multiple include_cpps in the same binary. The test case has them in the same rust file,...

Types with non-type template parameters turn into integers of the wrong size

8

If I have a C++ class with a member function that interacts with a `std::chrono::time_point` instantiation by value, autocxx generates wrappers that replace `time_point` with an integer type. My full...

Types with inaccessible destructors may still be freed by Rust

1

## Expected Behavior Refuse to allow freeing C++ objects with inaccessible destructors. Constructible C++ classes with non-public destructors are uncommon in my experience, but the ones that do exist are...

C++ methods with reference qualifiers result in non-compiling wrappers

1

## Expected Behavior Either ignore them or generate usable wrappers. I don't see a problem with ref-qualified methods, but rvalue-ref-qualified ones should probably be ignored because there's no good Rust...

Explicitly defaulted default/copy/move constructors are treated as present

2

## Expected Behavior They should be handled the same as implicitly defaulted constructors (aka no user-defined ones). This means they may be deleted or present, depending on the members and...