architectures other than 64-bit Intel or 64-bit ARM (for example a 32-bit or RISC-V machine)
However, zed currently fails to build on RISC-V because of an (indirect) dependency on ring 0.16, which does not support RISC-V. Version 0.17 of the crate does, but updating that dependency is not straightforward to me (not being a Rust developer). The compatibility seems restricted by rustls and async-tungstenite, but bumping those dependencies to resp. 0.21.8 and 0.25 (which are the minimum versions that are compatible with ring 0.17) results in the introduction of http 1.1.0, which is incompatible with version 0.2.12 of the http crate that's used by other dependencies.
Would it be possible to upgrade dependencies in order to unblock RISC-V support? ring 0.16.20 is 3 years old, rustls 0.20.3 is over 2 years old, so it seems that upgrading these dependencies is a good idea anyway.
If applicable, add mockups / screenshots to help present your vision of the feature
Check for existing issues
Describe the feature
The manual currently states:
However, zed currently fails to build on RISC-V because of an (indirect) dependency on ring 0.16, which does not support RISC-V. Version 0.17 of the crate does, but updating that dependency is not straightforward to me (not being a Rust developer). The compatibility seems restricted by rustls and async-tungstenite, but bumping those dependencies to resp. 0.21.8 and 0.25 (which are the minimum versions that are compatible with ring 0.17) results in the introduction of http 1.1.0, which is incompatible with version 0.2.12 of the http crate that's used by other dependencies.
Would it be possible to upgrade dependencies in order to unblock RISC-V support? ring 0.16.20 is 3 years old, rustls 0.20.3 is over 2 years old, so it seems that upgrading these dependencies is a good idea anyway.
If applicable, add mockups / screenshots to help present your vision of the feature
No response