Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Sat, 14 Feb 2015 16:28:11 +0000 (UTC)
From: "Stephan Ewen (JIRA)" <jira@apache.org>
To: issues@flink.incubator.apache.org
Message-ID: <JIRA.12775149.1423931272000.48047.1423931291497@Atlassian.JIRA>
In-Reply-To: <JIRA.12775149.1423931272000@Atlassian.JIRA>
References: <JIRA.12775149.1423931272000@Atlassian.JIRA>
 <JIRA.12775149.1423931272726@arcas>
Subject: [jira] [Created] (FLINK-1548) [DISCUSS] Make Scala implicit
 parameters explicit in the runtime
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Stephan Ewen created FLINK-1548:
-----------------------------------

             Summary: [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
            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)