You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this is more than an encoding of the first two snippets as it hides the inference of D, so that you can specify S, but not D (unless you supply the implicit argument explicitly)
(Conceptually, it would be even nicer to be able to write the following, emphasizing the similarity between implicit arguments and type parameters)
It could work by re-arranging argument lists behind the scenes, possibly splitting up the
implicit argument list, so that the current left-to-right ordering requirement is upheld: types can only depend on arguments on their left.
This is related to the multiple type parameter lists generalisation:
motivational examples from test/files/pos/depmet_implicit_oopsla_session_2.scala and neg/depmet_try_implicit.scala
can we relax the ordering restrictions on dependencies so that we can write
this is more than an encoding of the first two snippets as it hides the inference of D, so that you can specify S, but not D (unless you supply the implicit argument explicitly)
(Conceptually, it would be even nicer to be able to write the following, emphasizing the similarity between implicit arguments and type parameters)
It could work by re-arranging argument lists behind the scenes, possibly splitting up the
implicit argument list, so that the current left-to-right ordering requirement is upheld: types can only depend on arguments on their left.
This is related to the multiple type parameter lists generalisation:
could be rewritten to:
The text was updated successfully, but these errors were encountered: