Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

No way to obtain the opcode of a BinaryExpr from the C API #29138

Closed
llvmbot opened this issue Jul 29, 2016 · 0 comments
Closed

No way to obtain the opcode of a BinaryExpr from the C API #29138

llvmbot opened this issue Jul 29, 2016 · 0 comments
Labels
bugzilla Issues migrated from bugzilla clang:as-a-library libclang and C++ API

Comments

@llvmbot
Copy link
Member

llvmbot commented Jul 29, 2016

Bugzilla Link 28768
Version trunk
OS Linux
Reporter LLVM Bugzilla Contributor

Extended Description

This results in anyone unable to use the C++ API (specifically, bindings) being unable to use libclang for actually parsing C, driving them to use other tools (such as the Haskell Language.C library).

Relevant:

Corrode didn't use libclang due to it missing this (among other things): jameysharp/corrode#50 (comment)

The libclang Rust bindings would support it if available: KyleMayes/clang-rs#5
@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bugzilla Issues migrated from bugzilla clang:as-a-library libclang and C++ API
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@llvmbot