| commit | 712b7f4efd2013e28af4dc7b85dbb21fc09caeaa | [log] [tgz] |
|---|---|---|
| author | Martin Brænne <mboehme@google.com> | Thu Jun 23 00:55:17 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jun 23 00:55:57 2022 -0700 |
| tree | 9cf025456e896b544349ac6a242e276c87fc5b1f | |
| parent | 4640933dbc013101d27e1595f2479f586369c6d7 [diff] |
Thread `TypeLoc` through `FunctionLifetimes` and `ValueLifetimes`. A followup CL will extract `annotate_type` attributes from the `TypeLoc`. Note: One might ask why all this mechanism is necessary. Couldn't the attribute arguments be placed on the `AttributedType`, so that we could extract them without having to access the `TypeLoc`? However, putting the attribute arguments on the `AttributedType` would violate the conceptual distinction between `Type` and `TypeLoc`. The attribute arguments are `Expr`s, which are associated with a specific location in the source code. In contrast, a `Type` is intended to be independent of source location. PiperOrigin-RevId: 456703847
Extremely experimental interop tooling for C++ and Rust.
Please don‘t use, this is an experiment and we don’t yet know where will it take us. There will be breaking changes without warning. Unfortunately, we can't take contributions at this point.
$ apt install clang lld bazel $ git clone git@github.com:google/crubit.git $ cd crubit $ bazel build --linkopt=-fuse-ld=/usr/bin/ld.lld //rs_bindings_from_cc:rs_bindings_from_cc_impl
$ git clone https://github.com/llvm/llvm-project $ cd llvm-project $ CC=clang CXX=clang++ cmake -S llvm -B build -DLLVM_ENABLE_PROJECTS='clang' -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=install $ cmake --build build -j $ # wait... $ cmake --install build $ cd ../crubit $ LLVM_INSTALL_PATH=../llvm-project/install bazel build //rs_bindings_from_cc:rs_bindings_from_cc_impl