Kyle J Strand

I believe this is potentially something for @rust-lang/wg-codegen to weigh in on?

Personally, I think `#[foo::bar::baz::(arg)]` would be much better than `#[foo(bar(baz(arg))))))]`. After all, we may have quite a few functional features, but this isn't Lisp! Two layers of paren-nesting, as in...

As an incremental improvement, could `jj edit` at least print a warning after the file is closed if the config is invalid and/or has unrecognized options? (My point of confusion...

Unfortunately, I don't think a new maintainer would be able to change the `smartstring` license to MIT or Apache-2, which is currently preventing me from using `rhai`. Looks like the...

@rudderbucky I'm not saying Rhai is doing anything wrong, merely that by being more restrictive than MIT, `smartstr` can prevent some (corporate) projects from using Rhai. That's not necessarily a...

@rudderbucky That's...not how licensing works. You're still using `smartstr` if you use Rhai, and therefore you must comply with its license. This is why tools like `cargo deny` perform _recursive_...

@rudderbucky Again, I'm not saying that `rhai` is being licensed incorrectly; it's fine for `rhai` to be Apache-2.0/MIT (as far as I know). I may be misunderstanding what you're saying...

@rudderbucky My point is that I wasn't sure I'd be able to use `smartstring` at all, _and therefore_ I wouldn't be able to use Rhai, because that entails using `smartstring`.

Related feature request in `nextest` itself: https://github.com/nextest-rs/nextest/discussions/2233

@taiki-e That doesn't appear to be compatible with the `--nextest-archive` option; or is it? It appears to assume that the tests are in a consolidated directory already.