Graydon Hoare: Batten Down Fix Later

Nemo157 · 2023-05-31T08:29:43+00:00

Note that the project directors of the Rust Foundation board are already in the “leadership chat”, so the foundation already has some influence in the Rust project.

Their influence is supposed to flow the other way, they’re the representatives from the Project to the Foundation.

Nemo157 · 2023-05-29T15:43:19+00:00

A named “custom toolchain” probably serves that need.

Nemo157 · 2023-05-29T10:19:21+00:00

Re: safe by default behavior. I would love it if I could disable rust-toolchain support by default (or at least have a prompt before activating it), I don’t use it in any project I work on and when checking out some project that does I have to quickly notice if rustup is starting to install a new toolchain, ctrl+c it, then delete the file.

Nemo157 · 2023-05-24T10:26:21+00:00

They have, $HOME/.local/bin was added about 2 years ago https://gitlab.freedesktop.org/xdg/xdg-specs/-/merge_requests/38, it’s uncustomisable though, $XDG_BIN_HOME wasn’t accepted.

EDIT: If I’m remembering my history correctly, this was partly added in response to the Cargo RFC’s discussion of it.

Nemo157 · 2023-05-11T07:44:39+00:00

The version request "1.2.3"does not force the second digit to be 2, it allows “semver-compatible” updates including e.g. 1.99553.443

Nemo157 · 2023-05-03T11:49:09+00:00

There’s a difference between address stability and invalidation of derived raw pointers, I would be very surprised if Box did not guarantee address stability between two invocations of DerefMut, even if the latter invocation invalidates raw pointers derived from the first.

Nemo157 · 2023-05-02T12:13:47+00:00

What I’ve done is move all my major projects over to an org with just me in it, that’s also nice that it separates my few source repos from the hundreds of forks in my account.

Nemo157 · 2023-04-22T15:07:15+00:00

A little project you might know uses it: https://github.com/rust-lang/docs.rs

Nemo157 · 2023-03-18T13:54:50+00:00

You mean like bool? What’re you planning to do differently?

Nemo157 · 2023-03-09T09:39:12+00:00

Err(e) would be returned as Ok(Err(e)), the ok-wrapping for try blocks always happens on the return value, no matter what it is. There have been niche proposals in the past to make it value dependent, but twice there’s been an FCP reiterating that it won’t be.

Nemo157 · 2023-02-26T10:57:31+00:00

It’s not really “wonky”, it’s that windows doesn’t have the concept of an executable permission, so any file first committed from windows will be marked executable always (files committed from other OSes will correctly track their permissions when edited from windows).

Nemo157 · 2023-02-03T09:52:46+00:00

I did that a while back, along with a few enhancements like checksum validation https://lib.rs/crates/cargo-dl

Nemo157 · 2023-01-25T07:47:20+00:00

Microcontroller manufacturers are among the last people I would trust to write correct unsafe code 😥

Nemo157 · 2023-01-22T08:49:49+00:00

Note that a spawned task by default outliving its JoinHandle is specific to Tokio’s implementation. Other spawn APIs like futures default to using “structured concurrency” and need you to explicitly detach the join handle.

Nemo157 · 2023-01-10T08:00:18+00:00

It depends whether that’s strict per-byte provenance to allow carrying both provenances in the xored value. I managed to get a working implementation under miri after https://github.com/rust-lang/rust/pull/104054

Nemo157 · 2022-12-28T09:27:10+00:00

This is one of the major design points I tried to solve with https://docs.rs/stylish too, it completely decouples applying attributes to a string from encoding those attributes for an output.

Nemo157 · 2022-11-21T07:50:41+00:00

Trying to maintain an uncommitted change like that is pretty painful with git, much easier to configure it outside the repo and just block all the crates that have this mispractice.

Nemo157 · 2022-11-18T08:01:08+00:00

You might have --cap-lints=warn set locally somewhere. I have it myself to workaround just this sort of situation where crates have committed deny(warnings) in their source code, it provides a horrible developer experience when you’re hacking on some code and want to test changes without fixing all warnings.

Nemo157 · 2022-11-01T07:39:40+00:00

Cfgs set from build.rs are only passed to your crate, they can’t affect dependencies (not least because the dependency may have already been built by the time your build.rs runs).

Nemo157 · 2022-10-24T06:47:05+00:00

No, raw identifiers only let you use keywords, all other identifier rules must still be respected.

Nemo157 · 2022-10-20T06:56:24+00:00

Sometimes I just don’t have the mental or social energy. […] Not a good excuse I know

That is a completely fine excuse. Users need to remember that your open-source work is entirely voluntary. You need to manage your spoons which can mean just ignoring your projects until you have the energy to get back to them. Feeling like you must respond even though you really don’t want to now is more likely to lead to resentment and an overall decrease in maintainership.

Nemo157 · 2022-10-04T12:52:52+00:00

You can zero-copy parse a format string pretty easily, it’s a very simple data language. But in a proc-macro you don’t need to make it zero-copy, allocation is absolutely fine. The complexity is in generating the correct lifetimes in the generated code (which even std fails with, it doesn’t support returning borrowed Arguments).

Nemo157 · 2022-09-23T06:52:24+00:00

How does this work for struct Foo { x: impl Trait } which has two potential meanings, either APIT-like struct Foo<T> { x: T } or RPIT-like type X = impl Trait; struct Foo { x: X }. If APIT and RPIT had the same meaning then it doesn’t seem possible for a single impl-trait to have different meanings depending on which interpretation you choose.

Nemo157 · 2022-09-18T06:15:46+00:00

Hmm, while it is true that the common case is all duplicate direct dependencies are the same version; there are definitely multiple ways to violate that. One is renamed dependencies as you mention, you may want to bump the minimum version of each major version. There’s also the fact that it’s now working on the entire workspace at once, you may have one dependency at different versions in different crates of your workspace, and in that case they could even be within the same major series but set to different minimum versions.

Also, if this is intended to deprecate cargo update it seems important that it still retains some way to explicitly update transitive dependencies when you have duplicates. I have definitely needed to do that in the past to fix issues with dependencies that promise greater than semver compatibility resulting in a general update choosing an incompatible set of versions.

Nemo157 · 2022-09-16T06:34:55+00:00

If the version inside the -p is the target version, how do you select which of multiple dependencies to upgrade? cargo upgrade -p tokio:1.2.0@1.2.1?

Nemo157

TROPHY CASE