Bilal Mahmoud

Update: if `CARGO_TEST_HACK_FLAGS_BASE` is defined in `base.toml` This issue does not occur: extend.toml: unchanged base.toml ```toml [config] default_to_workspace = false [config.modify_core_tasks] private = true namespace = "default" [env] CARGO_TEST_HACK_FLAGS_BASE =...

Thanks for the reply. This is pretty unintuitive because of the following: The value isn't replaced with an empty string but instead with the value that isn't split. What I...

That's also what I expect, but my case is base env2 = y extended env1 = y env2 = ${env1} That env2 is also y, which in the current case...

Sorry, I misunderstood. I see what you mean now. This makes sense. It's all about trade-offs. I am still confused about why the string is inserted into the arguments. Do...

I think I finally know where the confusion is coming from. With my suggestion base env1 = x env2 = ${env1} extended env1 = y result env1 = y env2...

> i can't remember if i'm changing it to empty string or leaving it as is when i can't find the env var. is that the case you are talking...

> right? Yes! that is what I want, but this isn't working as intended (at least from what I understood) ``` base # NOT DEFINE -> env1 = x env2...

There are also things like: https://docs.rs/binread/latest/binread/attribute/index.html, which create an additional documentation-only module.

This PR implements a hook-based serialization (like #794) and a new attachment kind for `serde` (like `attach_printable`). I am unsure if we should keep both or decide on one of...

I know that `attach_printable` is planned for removal once `specialization` hits. I haven't thought about the ramifications that every type needs to be a strict subset. This, of course, makes...