hohn/codeql
1
0
Fork 0
mirror of https://github.com/github/codeql.git synced 2025-12-16 16:53:25 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
45c0c46c9d0139caa252344080deb12672ee6a9f
codeql/rust/ast-generator
History
Paolo Tranquilli 45c0c46c9d Cargo: align rust toolchain version with internal repository 
Also:
* remove new warnings raised by the rust toolchain
* run new formatting and linting
* update the rust toolchain used by `cargo`

While we keep `bazel` builds using the same toolchain as internally
(now a nightly one), I opted for using a stable toolchain for `cargo`.
The nightly toolchain is only required internally for build reasons, we
should keep not using any unstable rust features in our sources.
2025-08-11 16:45:47 +02:00
..
patches
Rust: update rust-analyzer
2025-01-08 11:14:08 +01:00
src
Cargo: align rust toolchain version with internal repository
2025-08-11 16:45:47 +02:00
templates
Rust: refactor pre_emit! and post_emit! to a trait
2025-06-24 10:40:33 +02:00
.gitignore
Rust: add local copy of rust.ungrammar
2025-03-21 09:48:29 +01:00
BUILD.bazel
Rust: expand attribute macros
2025-04-25 16:16:49 +02:00
BUILD.rust-analyzer-src.bazel
Rust: fetch ungram and rust-analyzer code instead of checking it in
2024-12-18 16:37:24 +01:00
Cargo.toml
Cargo: run upgrade
2025-06-20 17:34:23 +02:00
README.md
Rust: fix typo in README.md
2025-06-12 13:00:23 +01:00

README.md

This crate takes care of generating ast.py in the schema and translate/generate.rs in the extractor.

It uses:

  • rust.ungram from ra_ap_syntax
  • a couple of slightly modified sources from rust-analyzer that are not published.

Both are fetched by bazel while building. In order to have proper IDE support and being able to run cargo tooling in this crate, you can run

bazel run //rust/ast-generator:inject-sources

which will create the missing sources. Be aware that bazel will still use the source taken directly from rust-analyzer, not the one in your working copy. Those should not need to be update often though.