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

86 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"
Set MSRV
2021-10-23 07:07:11 -05:00
rust-version = "1.56"
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]
Update versions
2020-02-18 07:57:41 -06:00
anyhow = "1.0.26"
Bump crossbeam-channel and lsp-server in rust-analyzer
2020-10-13 10:05:06 -05:00
crossbeam-channel = "0.5.0"
Split textDocument/formatting TextEdit with diff
2020-12-31 06:05:19 -06:00
dissimilar = "1.0.2"
Update crates
2020-12-30 09:39:50 -06:00
itertools = "0.10.0"
Sort deps
2020-02-17 10:41:53 -06:00
jod-thread = "0.1.0"
Pull in new lsp-types for VS compat
2021-10-14 01:37:57 -05:00
lsp-types = { version = "0.91", features = ["proposed"] }
Bump deps
2020-06-27 02:09:47 -05:00
parking_lot = "0.11.0"
:arrow_up: xflags
2021-03-06 14:02:06 -06:00
xflags = "0.2.1"
Replace rand with oorandom
2020-07-29 12:49:10 -05:00
oorandom = "11.1.2"
Update versions
2020-02-18 07:57:41 -06:00
rustc-hash = "1.1.0"
Bump deps
2020-05-01 07:29:03 -05:00
serde = { version = "1.0.106", features = ["derive"] }
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 08:31:24 -06:00
serde_json = { version = "1.0.48", features = ["preserve_order"] }
Sort deps
2020-02-17 10:41:53 -06:00
threadpool = "1.7.1"
Bump deps
2020-10-24 09:10:27 -05:00
rayon = "1.5"
Setup global allocator in the correct crate It worked before, but was roundabout
2020-07-22 06:42:53 -05:00
mimalloc = { version = "0.1.19", default-features = false, optional = true }
Return ServerNotInitialized according to the spec According to the spec we should return ServerNotInitialized if the server is waiting for an initialize request and something else comes in. Upgrading to lsp-server 0.5.1 will do this and retry until the initialize request comes in. Fixes #8581
2021-04-27 06:47:06 -05:00
lsp-server = "0.5.1"
Add tracing to main rust-analyzer binary
2020-10-23 10:07:06 -05:00
tracing = "0.1"
Pull in new lsp-types for VS compat
2021-10-14 01:37:57 -05:00
tracing-subscriber = { version = "0.2", default-features = false, features = [
"env-filter",
"registry",
"fmt",
"tracing-log",
] }
switch `log` crate to `tracing`
2021-08-15 07:46:13 -05:00
tracing-log = "0.1.2"
update to tracing-tree 0.1.10, which does not pull in syn.
2021-09-06 09:33:08 -05:00
tracing-tree = { version = "0.1.10" }
Make always-assert crate reusable
2021-01-26 13:11:12 -06:00
always-assert = "0.1"
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]
Update versions
2020-02-18 07:57:41 -06:00
winapi = "0.3.8"
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]
Use package renaming so source doesn't say tikv
2021-05-07 14:41:07 -05:00
jemallocator = { version = "0.4.1", 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]
internal: update expect
2021-10-09 09:17:16 -05:00
expect-test = "1.2.0-pre.1"
internal: make `xtask` lighter Moving tests to `rust-analyzer` crate allows removing walkdir dependency from `xtask`. It does seem more reasonable to keep tidy tests outside of the "build system" and closer to other integration tests.
2021-07-04 04:42:35 -05:00
xshell = "0.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