# Workspace + warrnigs/errors

**URL:** https://internals.rust-lang.org/t/workspace-warrnigs-errors/6683
**Category:** compiler
**Created:** [February 1, 2018, 1:19pm UTC](https://internals.rust-lang.org/t/workspace-warrnigs-errors/6683 "2018-02-01T13:19:17Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![davemilter](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/davemilter/32/3493_2.png) [@davemilter](https://internals.rust-lang.org/u/davemilter)
#### Post date: [February 1, 2018, 1:19pm UTC](https://internals.rust-lang.org/t/workspace-warrnigs-errors/6683/1 "2018-02-01T13:19:17Z")

</div>

Current nightly `rustc 1.25.0-nightly (8ccab7eed 2018-01-31)` change handling of workspace. At now if you compile code inside crate, that part of workspace it print warnings/errors in form of `crate/src/foo.rs:X:Y` instead of `src/foo.rs:X:Y`.

Anybody know why this change was done?

It breaks many tools, for example `emacs + rust-mode` becomes unusable - for each error it ask me where to find file, because of it expects that if you run compiler in directory `workspace/crate`, the all paths should be relative to `crate` or absolute, but at now all paths relative to `worskspace`. intellij-rust also not show errors with nightly [https://users.rust-lang.org/t/intellij-rust-and-compile-errors/15103/7](https://users.rust-lang.org/t/intellij-rust-and-compile-errors/15103/7)

I do not know about intellij, but for emacs this not configurable behaviour, so it requires implementation of something like `rust-compile-mode` and it is not the simple thing. May be it is possible somehow turn off this new **feature**?

---

<div class="post-metadata">

### Author: ![matklad](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/matklad/32/12266_2.png) [@matklad](https://internals.rust-lang.org/u/matklad)
#### Post date: [February 1, 2018, 1:57pm UTC](https://internals.rust-lang.org/t/workspace-warrnigs-errors/6683/2 "2018-02-01T13:57:52Z")

</div>

Yep, this is a known problem. It was implemented in [https://github.com/rust-lang/cargo/pull/4788](https://github.com/rust-lang/cargo/pull/4788), and we are figuring out how to solve the original problem without breaking the world (you can access the scale of the problem by the number of linked issues 🙂

---

<div class="post-metadata">

### Author: ![davemilter](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/davemilter/32/3493_2.png) [@davemilter](https://internals.rust-lang.org/u/davemilter)
#### Post date: [February 1, 2018, 2:09pm UTC](https://internals.rust-lang.org/t/workspace-warrnigs-errors/6683/3 "2018-02-01T14:09:29Z")

</div>

Thanks, looks rather strange, why internal caching requires change of visible behaviour (output to stdout/stdserr). Then I am going to report bug.

---

<div class="post-metadata">

### Author: ![davemilter](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/davemilter/32/3493_2.png) [@davemilter](https://internals.rust-lang.org/u/davemilter)
#### Post date: [February 1, 2018, 10:18pm UTC](https://internals.rust-lang.org/t/workspace-warrnigs-errors/6683/4 "2018-02-01T22:18:33Z")

</div>

There is intention to fix this regression:

> <https://github.com/rust-lang/rust/issues/47939>

---

<div class="post-metadata">

### Author: ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/system/32/14092_2.png) [@system](https://internals.rust-lang.org/u/system)
#### Post date: [March 25, 2019, 8:29am UTC](https://internals.rust-lang.org/t/workspace-warrnigs-errors/6683/5 "2019-03-25T08:29:36Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
