mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
d312b4519a
rust/crates/rust-analyzer/Cargo.toml

87 lines
2.6 KiB
TOML
Raw Normal View History

Start lang server
2018-08-10 07:07:43 -05:00
[package]
Rename the binary to rust-analyzer
2020-02-18 05:33:16 -06:00
name = "rust-analyzer"
Rename ra_ide -> ide
2020-08-13 10:42:52 -05:00
version = "0.0.0"
Added some metadata for rust-analyser package sufficient to build it using `cargo deb` Co-authored-by: bjorn3 <bjorn3@users.noreply.github.com>
2021-07-19 07:39:49 -05:00
authors = ["rust-analyzer Team"]
homepage = "https://github.com/rust-analyzer/rust-analyzer"
description = "A language server for the Rust programming language"
documentation = "https://rust-analyzer.github.io/manual.html"
Rename ra_ide -> ide
2020-08-13 10:42:52 -05:00
license = "MIT OR Apache-2.0"
Better folder structure
2020-02-18 04:56:18 -06:00
autobins = false
Migrate to edition 2021
2021-10-21 10:49:28 -05:00
edition = "2021"
Bump MSRV (1.57)
2021-12-15 14:49:48 -06:00
rust-version = "1.57"
Start lang server
2018-08-10 07:07:43 -05:00
Disable doctests
2019-11-17 09:35:05 -06:00
[lib]
doctest = false
Better folder structure
2020-02-18 04:56:18 -06:00
[[bin]]
Rename the binary to rust-analyzer
2020-02-18 05:33:16 -06:00
name = "rust-analyzer"
Remove unneeded "./" prefix affecting error messages Before: error[E0599]: no method named `initialize_finish` found for struct `lsp_server::Connection` in the current scope --> crates/rust-analyzer/./src/bin/main.rs:99:16 | 99 | connection.initialize_finish(initialize_id, initialize_result)?; | ^^^^^^^^^^^^^^^^^ method not found in `lsp_server::Connection` After: error[E0599]: no method named `initialize_finish` found for struct `lsp_server::Connection` in the current scope --> crates/rust-analyzer/src/bin/main.rs:99:16 | 99 | connection.initialize_finish(initialize_id, initialize_result)?; | ^^^^^^^^^^^^^^^^^ method not found in `lsp_server::Connection`
2020-06-03 20:01:24 -05:00
path = "src/bin/main.rs"
Better folder structure
2020-02-18 04:56:18 -06:00
Start lang server
2018-08-10 07:07:43 -05:00
[dependencies]
minor: Bump dependencies
2022-03-22 11:36:41 -05:00
anyhow = "1.0.56"
crossbeam-channel = "0.5.4"
dissimilar = "1.0.3"
itertools = "0.10.3"
lsp-types = { version = "0.92.1", features = ["proposed"] }
parking_lot = "0.12.0"
xflags = "0.2.4"
oorandom = "11.1.3"
Update versions
2020-02-18 07:57:41 -06:00
rustc-hash = "1.1.0"
minor: Bump dependencies
2022-03-22 11:36:41 -05:00
serde = { version = "1.0.136", features = ["derive"] }
serde_json = { version = "1.0.79", features = ["preserve_order"] }
threadpool = "1.8.1"
rayon = "1.5.1"
cleanup + detect num cpus
2022-01-14 03:48:59 -06:00
num_cpus = "1.13.1"
minor: Bump dependencies
2022-03-22 11:36:41 -05:00
mimalloc = { version = "0.1.28", default-features = false, optional = true }
lsp-server = "0.5.2"
tracing = "0.1.32"
tracing-subscriber = { version = "0.3.9", default-features = false, features = [
Pull in new lsp-types for VS compat
2021-10-14 01:37:57 -05:00
"env-filter",
"registry",
"fmt",
"tracing-log",
] }
switch `log` crate to `tracing`
2021-08-15 07:46:13 -05:00
tracing-log = "0.1.2"
minor: Bump dependencies
2022-03-22 11:36:41 -05:00
tracing-tree = "0.2.0"
always-assert = "0.1.2"
internal: reduce crate interdependence I don't think there's anything wrong with project_model depending on proc_macro_api directly -- fundamentally, both are about gluing our pure data model to the messy outside world. However, it's easy enough to avoid the dependency, so why not. As an additional consideration, `proc_macro_api` now pulls in `base_db`. project_model should definitely not depend on that!
2021-08-22 05:32:00 -05:00
Allow rust-analyzer auto publishing
2020-08-24 10:27:13 -05:00
stdx = { path = "../stdx", version = "0.0.0" }
flycheck = { path = "../flycheck", version = "0.0.0" }
ide = { path = "../ide", version = "0.0.0" }
Move the helpers into ide_db
2020-11-28 08:30:39 -06:00
ide_db = { path = "../ide_db", version = "0.0.0" }
Allow rust-analyzer auto publishing
2020-08-24 10:27:13 -05:00
profile = { path = "../profile", version = "0.0.0" }
project_model = { path = "../project_model", version = "0.0.0" }
syntax = { path = "../syntax", version = "0.0.0" }
vfs = { path = "../vfs", version = "0.0.0" }
vfs-notify = { path = "../vfs-notify", version = "0.0.0" }
cfg = { path = "../cfg", version = "0.0.0" }
toolchain = { path = "../toolchain", version = "0.0.0" }
internal: remove unreasonable crate dependency Proc macro expansion shouldn't know about salsa at all.
2021-08-22 06:05:12 -05:00
tt = { path = "../tt", version = "0.0.0" }
internal: reduce crate interdependence I don't think there's anything wrong with project_model depending on proc_macro_api directly -- fundamentally, both are about gluing our pure data model to the messy outside world. However, it's easy enough to avoid the dependency, so why not. As an additional consideration, `proc_macro_api` now pulls in `base_db`. project_model should definitely not depend on that!
2021-08-22 05:32:00 -05:00
proc_macro_api = { path = "../proc_macro_api", version = "0.0.0" }
Add an integration test
2018-09-01 12:21:11 -05:00
Merge cli and ra_lsp_server
2020-02-17 12:03:03 -06:00
# This should only be used in CLI
7526: Renamed create ssr to ide_ssr.
2021-02-22 13:14:58 -06:00
ide_ssr = { path = "../ide_ssr", version = "0.0.0" }
Allow rust-analyzer auto publishing
2020-08-24 10:27:13 -05:00
hir = { path = "../hir", version = "0.0.0" }
hir_def = { path = "../hir_def", version = "0.0.0" }
hir_ty = { path = "../hir_ty", version = "0.0.0" }
proc_macro_srv = { path = "../proc_macro_srv", version = "0.0.0" }
Merge cli and ra_lsp_server
2020-02-17 12:03:03 -06:00
Bump main thread priority on windows
2020-01-26 05:02:56 -06:00
[target.'cfg(windows)'.dependencies]
minor: Bump dependencies
2022-03-22 11:36:41 -05:00
winapi = "0.3.9"
Bump main thread priority on windows
2020-01-26 05:02:56 -06:00
Add back jemalloc support
2021-01-18 12:25:55 -06:00
[target.'cfg(not(target_env = "msvc"))'.dependencies]
minor: Bump dependencies
2022-03-22 11:36:41 -05:00
jemallocator = { version = "0.4.3", package = "tikv-jemallocator", optional = true }
Add back jemalloc support
2021-01-18 12:25:55 -06:00
Add an integration test
2018-09-01 12:21:11 -05:00
[dev-dependencies]
minor: Bump dependencies
2022-03-22 11:36:41 -05:00
expect-test = "1.2.2"
jod-thread = "0.1.2"
Bump xshell and fix dist
2022-03-17 01:53:33 -05:00
xshell = "0.2.1"
internal: overhaul code generation * Keep codegen adjacent to the relevant crates. * Remove codgen deps from xtask, speeding-up from-source installation. This regresses the release process a bit, as it now needs to run the tests (and, by extension, compile the code).
2021-07-03 14:11:03 -05:00
extract fixture parsing
2018-10-31 13:37:32 -05:00
test_utils = { path = "../test_utils" }
internal: overhaul code generation * Keep codegen adjacent to the relevant crates. * Remove codgen deps from xtask, speeding-up from-source installation. This regresses the release process a bit, as it now needs to run the tests (and, by extension, compile the code).
2021-07-03 14:11:03 -05:00
sourcegen = { path = "../sourcegen" }
Rename ra_mbe -> mbe
2020-08-13 03:08:11 -05:00
mbe = { path = "../mbe" }
Add back jemalloc support
2021-01-18 12:25:55 -06:00
[features]
Use package renaming so source doesn't say tikv
2021-05-07 14:41:07 -05:00
jemalloc = ["jemallocator", "profile/jemalloc"]
Make always-assert crate reusable
2021-01-26 13:11:12 -06:00
force-always-assert = ["always-assert/force"]
Reference in New Issue Copy Permalink