Imbris

I recently had a chance to try both heaptrack and bytehound on a memory leak issue. Previously I have used heaptrack but this was my first time trying bytehound. Here...

I think this is also an instance of https://github.com/rust-lang/unsafe-code-guidelines/issues/256 With `Tower` being a ZST, under SB a `&Tower` will only have permission to access 0 bytes. ```rs /// The tower...

I experimented with some changes fixing this SB violation on top of the `epoch-fix-sb-violations` branch: https://github.com/Imberflur/crossbeam/commit/9156396d067a27590b982f5382f44e0c71c51b65 This commit passes: ```sh MIRIFLAGS="-Zmiri-disable-isolation -Zmiri-ignore-leaks" \ cargo miri test -p crossbeam-skiplist ```

The SB error with `IsElement` looks like a case of https://github.com/rust-lang/unsafe-code-guidelines/issues/256 With SB the provenance of references is restricted to the range of the type that the reference points to....

I encountered a similar problem where some group of tests would conflict on some resource and thus need to be run one at a time to have exclusive access to...

closing since the question was answered

Closing since this seems to be answered. If further discussion is needed please re-open or open another issue!

> A potential improvement is to allow multiple `Write`'s to be held, but only panic if both are dereferenced together. I haven't gotten familiar with the code to implement that...

Latest docs include this https://docs.rs/specs/0.18.0/specs/storage/struct.PairedStorage.html#method.get_mut_unchecked

I saw another approach here of putting a less used task with more dependencies behind a feature and then having the xtask rebuild itself with the required features if necessary:...