Joshua Brest (杰成)
Joshua Brest (杰成)
> Even assuming I agreed that's bad practice (which, I don't), it is not clear how that motivation has lead to this proposed change. How can I make this RFC...
> Is your thinking that an expansion of inference will let people import less types, and then that would cause them to use glob imports less? Part of it yes,...
> s (set A) is encountered as the top-level expression in the following positions (set B), the `_` token in the expression form should be treated as **the type expected...
> One interesting quirk to think about (although unlikely): > > ```rust > fn foo(t: T) {} > > foo(_::default()) > ``` > > should this be allowed? we are...
> And honestly, it's a bit weird to me to realise how relatively okay I am with glob imports in Rust, considering how I often despise them in other languages...
> Personally `_::new()` and `_::Variant` "look wrong" to me although i cant tell why, I would expect `::new()` and `::Variant` to be the syntax, no suggestion on `_ { ......
> * According to this RFC, the `_` should be resolved to `Foo` (the function argument's type), but this isn't always correct. I suspect that this behavior is often useful...
I am currently traveling and am unable to review and respond affectively without my computer. Could I give someone write access?
> Could you add "Mythic.zip" to the 0.4.1 Tag? I have defined to download Mythic build from tags in Homebrew Cask (`https://github.com/MythicApp/Mythic/releases/download/v#{version}/Mythic.zip`). Optionally please provide me a direct link to...
Did you find a solution? @andersk ???