auto merge of #17019 : steveklabnik/rust/remove_compromise, r=thestinger
@dherman doesn't like it 😄
This commit is contained in:
commit
57781c3c30
|
@ -765,7 +765,7 @@ This is a deliberate design decision. While full-program inference is possible,
|
||||||
languages which have it, like Haskell, often suggest that documenting your
|
languages which have it, like Haskell, often suggest that documenting your
|
||||||
types explicitly is a best-practice. We agree that forcing functions to declare
|
types explicitly is a best-practice. We agree that forcing functions to declare
|
||||||
types while allowing for inference inside of function bodies is a wonderful
|
types while allowing for inference inside of function bodies is a wonderful
|
||||||
compromise between full inference and no inference.
|
sweet spot between full inference and no inference.
|
||||||
|
|
||||||
What about returning a value? Here's a function that adds one to an integer:
|
What about returning a value? Here's a function that adds one to an integer:
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue