[
https://issues.apache.org/jira/browse/FLINK-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-1548.
---------------------------------
Resolution: Fixed
Assignee: Stephan Ewen
Resolved through mailing list discussion (see archive:
http://mail-archives.apache.org/mod_mbox/flink-dev/201502.mbox/%3C48F7533F-FA7B-450F-8DD0-383FF8230349%40kth.se%3E).
Moved to Wiki Page
https://cwiki.apache.org/confluence/display/FLINK/Coding+Guidelines+for+Scala
> [DISCUSS] Make Scala implicit parameters explicit in the runtime
> ----------------------------------------------------------------
>
> Key: FLINK-1548
> URL: https://issues.apache.org/jira/browse/FLINK-1548
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Runtime
> Affects Versions: 0.9
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Priority: Minor
> Fix For: 0.9
>
>
> Scala's feature of implicit parameters is very powerful and invaluable in the
> design of nice high level APIs.
> In the system runtime, thought, I think we should not use implicit
> parameters, as they make the code more tricky to understand and make it
> harder to figure out where parameters actually come from. The API niceties
> are not required there. I propose to make all parameters explicit in runtime
> classes. Right now, this concerns mostly ActorSystem and Timeout parameters.
> This is nothing we need to do as a separate task, I would suggest to change
> that whenever we encounter such a method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
