From a2590db3f59b6f8c854354a6a1b5cbbf75bdd318 Mon Sep 17 00:00:00 2001 From: kerr Date: Fri, 7 Dec 2018 03:37:28 +0800 Subject: [PATCH] Add description about default method parameters. --- CONTRIBUTING.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 419dbe42b3..6c7e1dcf88 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -440,7 +440,8 @@ Scala has proven the most viable way to do it, as long as you keep the following 1. Traits that are part of the Java API should only be used to define pure interfaces, as soon as there are implementations of methods, prefer `abstract class`. - + +1. Any method definition in a class that will be part of the Java API should not use any default parameters, as they will show up ugly when using them from Java, use plain old method overloading instead. ### Overview of Scala types and their Java counterparts