| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2022-07-18 | Improve file watcher config | Jonas Schievink | -1/+1 | |
| 2022-06-28 | fix: Report proc macro errors in expressions correctly as well | Florian Diebold | -9/+10 | |
| They didn't have a krate before, resulting in the generic "proc macro not found" error. Also improve error messages a bit more. | ||||
| 2022-06-15 | Show proc-macro loading errors in unresolved-proc-macro diagnostics | Lukas Wirth | -35/+27 | |
| 2022-06-15 | fix: Clear proc-macro changed flag when reloading workspace | Lukas Wirth | -1/+1 | |
| 2022-06-12 | fix: Pass the build data to rustc_private crates | Lukas Wirth | -1/+7 | |
| 2022-05-23 | Keep the other `is` in `reload.rs` docs | DQ | -1/+1 | |
| 2022-05-23 | Fix typo in new `reload.rs` docs | DQ | -1/+1 | |
| Just skimmed today's changelog and came across the repetition | ||||
| 2022-05-21 | internal: document overall approach to reload | Aleksey Kladov | -1/+14 | |
| 2022-05-20 | Clear `cargo check` diagnostics when flycheck is turned off | Jonas Schievink | -0/+1 | |
| 2022-05-19 | simplify | Jonas Schievink | -7/+8 | |
| 2022-05-06 | Try not to invalidate our state when the proc macro preference didn't change | Laurențiu Nicola | -4/+7 | |
| 2022-05-02 | Auto merge of #12093 - nico-abram:uwu, r=Veykril | bors | -0/+5 | |
| Reload project on .cargo/config[.toml] changes Fixes #11024 Not adding tests as discussed in the issue | ||||
| 2022-04-29 | small typo in log message | Justin Tracey | -1/+1 | |
| 2022-04-27 | Reload project on .cargo/config[.toml] changes | unknown | -0/+5 | |
| Fixes #11024 | ||||
| 2022-04-18 | More visibility for switch workspaces and its states | Edwin Cheng | -2/+7 | |
| 2022-04-16 | internal: more visibility into why things happen | Aleksey Kladov | -4/+6 | |
| 2022-04-14 | internal: Show more project building errors to the user | Lukas Wirth | -33/+30 | |
| 2022-01-06 | Regenrate docs and package.json | Lukas Wirth | -3/+3 | |
| 2022-01-06 | feat: Add config to replace specific proc-macros with dummy expanders | Lukas Wirth | -8/+43 | |
| 2022-01-01 | feat: correctly fallback to notify if the clinet-side file watching is not ↵ | Aleksey Kladov | -31/+26 | |
| supported | ||||
| 2021-10-30 | Set server status to warning when proc-macro sources change | Lukas Wirth | -0/+5 | |
| 2021-10-16 | more clippy fixes | Milo | -2/+2 | |
| 2021-09-13 | Merge #10199 | bors[bot] | -52/+36 | |
| 10199: fix: Fix Cargo.toml change detection r=lnicola a=lnicola Maybe fixes #9546 Co-authored-by: Laurențiu Nicola <lnicola@dend.ro> | ||||
| 2021-09-13 | Shuffle code around to avoid an allocation | Laurențiu Nicola | -52/+36 | |
| 2021-09-07 | Rename `is_member` to `is_local` | Jonas Schievink | -3/+3 | |
| 2021-08-31 | internal: reduce coupling | Aleksey Kladov | -4/+5 | |
| tt is a data structure, data structures cant' go wrong, they shouldn't have the knowledge that the world outside of them has all kinds of errors. | ||||
| 2021-08-31 | internal: cleanup proc macro server error handlig | Aleksey Kladov | -4/+30 | |
| When dealing with proc macros, there are two very different kinds of errors: * first, usual errors of "proc macro panicked on this particular input" * second, the proc macro server might day if the user, eg, kills it First kind of errors are expected and are a normal output, while the second kind are genuine IO-errors. For this reason, we use a curious nested result here: `Result<Result<T, E1>, E2>` pattern, which is 100% inspired by http://sled.rs/errors.html | ||||
| 2021-08-31 | minor: improve readability | Aleksey Kladov | -6/+6 | |
| naming, layout & comments help! | ||||
| 2021-08-30 | internal: make scheduling control flow more obvious | Aleksey Kladov | -42/+7 | |
| There should be only one place where we need to check if we want to start background activities. | ||||
| 2021-08-30 | switch `log` crate to `tracing` | Dezhi Wu | -9/+9 | |
| 2021-08-25 | Fix reporting of build script errors | Jonas Schievink | -7/+17 | |
| 2021-08-25 | Don't fetch build script output twice | Jonas Schievink | -8/+0 | |
| 2021-08-22 | internal: remove unreasonable crate dependency | Aleksey Kladov | -4/+40 | |
| Proc macro expansion shouldn't know about salsa at all. | ||||
| 2021-08-22 | internal: reduce crate interdependence | Aleksey Kladov | -5/+11 | |
| 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-07-26 | internal: prepare to track changes to mem_docs | Aleksey Kladov | -1/+1 | |
| 2021-07-18 | fix: potential bugs when build scripts do not match the current project | Aleksey Kladov | -39/+67 | |
| 2021-07-18 | internal: simplify handling of the build scripts | Aleksey Kladov | -30/+61 | |
| 2021-07-17 | internal: a bit more of cwd safety for flycheck | Aleksey Kladov | -5/+6 | |
| 2021-06-29 | Watch for Cargo.toml and .lock changes | Laurențiu Nicola | -1/+7 | |
| 2021-06-03 | Make it opt-in | Jonas Schievink | -0/+6 | |
| 2021-05-25 | Check for subdirs in vfs loader exclusions. | ammkrn | -1/+5 | |
| The current logic used to transfer global_excludes into vfs exclusions only transfers global_excludes that are the parent of an item in dirs.include. This commit additionally adds an item from global_exclude to the vfs exclusions if the global_exclude is a child of an included item. | ||||
| 2021-05-23 | Drag detached files towards loading | Kirill Bulatov | -2/+8 | |
| 2021-05-23 | Draft detached files retrieval | Kirill Bulatov | -0/+1 | |
| 2021-04-22 | Add profiling spans under cargo_to_crate_graph | Laurențiu Nicola | -0/+1 | |
| 2021-04-12 | fix: don't spam repeated error messages when `cargo check` fails | Aleksey Kladov | -7/+8 | |
| Conceptually, using a *message* here is wrong, because this is a "status", rather than "point in time" thing. But statuses are an LSP extension, while messages are stable. As a compromise, send message only for more critical `metadata` failures, and only once per state change. | ||||
| 2021-04-06 | feat: show errors from `cargo metadata` and initial `cargo check` in the ↵ | Aleksey Kladov | -11/+30 | |
| status bar closes #3155 | ||||
| 2021-04-06 | More robust status notifications | Aleksey Kladov | -52/+67 | |
| 2021-04-06 | Use autoreload config to gate execution rather that staleness | Aleksey Kladov | -5/+1 | |
| 2021-04-06 | Improve readability | Aleksey Kladov | -29/+28 | |
| It's better to order functions in the order they are called, if there's ordering between them. | ||||
| 2021-04-06 | internal: do not drop errors from cargo metadata/check | Aleksey Kladov | -40/+36 | |
| Work towards #3155 | ||||
 |
index : rust | |
| https://github.com/rust-lang/rust |
| about summary refs log tree commit diff |