rust-lang / rust-lang/rust-bindgen
Getting the type of a method generates dubious results.
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 5.3k
- Forks
- 829
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 15
Description
Testcase:
class Bar;
class Foo
{
public:
void bar(Bar&);
typedef decltype(&Foo::bar) Getter;
};
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides a C++ testcase using decltype(&Foo::bar), but names no source file or test. Start by reproducing it in rust-bindgen and tracing how the method pointer type is handled; determine the expected generated binding and add a regression test when the intended result is established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100