Vitalii Kryvenko

Yes, here is a quick fix https://github.com/rust-marker/marker/pull/313

Btw. did something change in the merge settings or did github break something? I see that merge commits are created: 

This fixed the problem, driver build on ARM succeeded. Also, cargo-release failed to publish because all crates are already published. I suppose you published them manually, but if you fixed...

Yeah, there can be a check in the release scripts that inspects the version tag the "release" workflow was run with. It should fail if the version tag already exists...

I think using `--message-format json` is better, because this way we can build everything with a single cargo build, which should in theory be faster. I suppose your suggestion for...

There is a problem with the `--message-format` approach. Error messages are emitted in JSON as well and `cargo marker` would need to forward them. This complicates things even more. Need...

I've been thinking of implementing iterator API for traversing the AST tree. There is a major problem with implementing such API in that the iterator's state needs to have a...

The problem occurs because the code tries to look up the definition of the item in HIR, but that item comes from a foreign crate. When the `TraitRef`'s `ItemId` is...

I'm thinking if we could just officially store the `MarkerContext` in a private thread local and get rid of `'ast` lifetimes threaded through basically all the code. Any method that...

My main point is that we already have quite a lot of methods that use `with_cx` internally to obtain a reference to `MarkerContext`. What if we say that *every method*...