Qi Xiao
Qi Xiao
Closing this as a dup of https://github.com/elves/elvish/issues/1564, please see the latest comment there.
> This breaks two reasonable expectations, IMO: > > * Expanding `$⟨something⟩` should reflect the RHS of a previous `set ⟨something⟩ = …` This is a great point. > *...
> Hmm. I also feel a bit uncomfortable with `$x[@]`, also because `@` is a perfectly fine key for a map. Sure, lists and maps are different things, but indexing...
It is not necessary to run `go vet` or `staticcheck` on multiple platforms. Setting `GOOS` and `GOARCH` is sufficient. The `check-gen` script does need to be run on multiple platforms....
Sounds legit. However, `
There's no support for pointing to a specific commit now, unfortunately. It shouldn't be too hard to add that feature though, epm is an Elvish module https://github.com/elves/elvish/blob/master/pkg/mods/epm/epm.elv
I don't feel too strongly about this, but guarding against _unintentional_ typos seems to be a good job for linters, and that would make this change unnecessary.
Well the linter should only flag code like `eq foo`, where there is _always_ only one argument and the command is meaningless (it's equivalent to just `put $true`). Invocations like...
> I guess I'm still confused why the compiler can't just complain when it sees `eq foo` or just `eq`. Why is it necessary to delegate that to a linter?...
A note on compiler warnings: Elvish does currently violate the "no warning" rule in that it emits deprecation warnings. But: - Deprecation warnings are ephemeral: deprecated features soon get removed,...