Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Remove relative_path dependency | Aleksey Kladov | 2020-07-08 | 1 | -29/+87 |
| | |||||
* | New VFS | Aleksey Kladov | 2020-06-23 | 1 | -3/+4 |
| | |||||
* | Anchor file-system operations to the file, and not to the source root. | Aleksey Kladov | 2020-06-16 | 1 | -4/+4 |
| | | | | | | | | | | | | | | | | Anchoring to the SourceRoot wont' work if the path is absolute: #[path = "/tmp/foo.rs"] mod foo; Anchoring to a file will. However, we *should* anchor, instead of just producing an abs path. I can imagine a situation where, for example, rust-analyzer processes crates from different machines (or, for example, from in-memory git branch), where the same absolute path in different crates might refer to different files in the end! | ||||
* | More direct signature for resolve_path | Aleksey Kladov | 2020-06-05 | 1 | -1/+1 |
| | |||||
* | Rename resolve_relative_path -> resolve_path | Aleksey Kladov | 2020-06-05 | 1 | -1/+1 |
| | | | | For things like `concant!(env!("OUT_DIR"))`, we need to support abs paths | ||||
* | Use `dyn Trait` for working with databse | Aleksey Kladov | 2020-03-16 | 1 | -2/+2 |
| | | | | | | | It improves compile time in `--release` mode quite a bit, it doesn't really slow things down and, conceptually, it seems closer to what we want the physical architecture to look like (we don't want to monomorphise EVERYTHING in a single leaf crate). | ||||
* | Get rid of DefDatabase2 | Aleksey Kladov | 2019-11-23 | 1 | -2/+2 |
| | |||||
* | Reduce visibility | Aleksey Kladov | 2019-11-04 | 1 | -4/+8 |
| | |||||
* | Reexport relative_path from ra_db | Aleksey Kladov | 2019-11-03 | 1 | -2/+1 |
| | |||||
* | move mod_resolution to hir_def | Aleksey Kladov | 2019-10-31 | 1 | -0/+77 |