jimmyfrasche

Does precedence mean the order the filters are applied in or which is used if both are given? If it's the order, then `-run` followed by `-skip` makes the most...

If viewing it as an error-correction why couldn't it be inserted whenever it encounters a non-literal token? That way it would only require an extraneous `&` or `@nest` when the...

It should be an error if it escapes, regardless of how it does so. But `SafeJoin("/a", "/a/b")` should work fine.

@OneOfOne Naked returns are fine for very short functions but are harder to scale: it gets too easy to accidentally return partially constructed values or the wrong err because of...

@rogpeppe `return ...aSlice` looks too much like https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Spread_operator That's not a strong argument against it, but I'd still rather not see it. While I would be surprised if this proposal...

@davecheney indeed. My argument is that the primary benefit of the succinct syntax is that it improves the *readability*. If it makes it easier to type that's just a bonus....

@bradfitz that seems like it could cause too much fun when the return signature changes in a long func or one of the return types now satisfies an interface. It...

My current thoughts on the three examples @robpike showed are 1. allow all three 2. discourage cases where `...` represents 0 return values by linting 3. have a tool that...

I don't care for either proposal. If you're writing CSS and want to do prefixing, you want it done everywhere applicable, which means you don't want to have to specify...

> Can you give me some complicated special cases? Old and new flexbox syntax and the changes to the default of flex: that need to be taken into account to...