IDEs AppCode CLion DataGrip DataSpell Fleet GoLand IntelliJ IDEA PhpStorm PyCharm RustRover Rider RubyMine WebStorm Plugins & Services Big Data Tools Code With Me Quality Assurance JetBrains Platform Scala Toolbox App Writerside JetBrains AI Grazie Team Tools Datalore Space TeamCity Upsource YouTrack Hub Qodana .NET & Visual Studio .NET Tools ReSharper C++ Languages & Frameworks Kotlin Ktor MPS Am
IDEs AppCode CLion DataGrip DataSpell Fleet GoLand IntelliJ IDEA PhpStorm PyCharm RustRover Rider RubyMine WebStorm Plugins & Services Big Data Tools Code With Me Quality Assurance JetBrains Platform Scala Toolbox App Writerside Team Tools Datalore Space TeamCity Upsource YouTrack Hub Qodana .NET & Visual Studio .NET Tools ReSharper C++ Languages & Frameworks Kotlin Ktor MPS Education & Research J
The builder pattern has proven to be a useful paradigm in the Java programming language when there are many parameters needed to construct an object. As Effective Java points out, constructors or factory methods with too many parameters become susceptible to bugs when parameters are accidentally swapped in clients. Kotlin’s named parameters solve this problem in many cases because a Kotlin caller
Kotlin is very smart under the hood. We cannot declare primitives in Kotlin, but they are used when we don’t use a variable like an object. For instance, look at the following example: var i = 10 i = i * 2 println(i)This declaration uses primitive int under the hood. This is its representation in Java: // Java int i = 10; i = i * 2; System.out.println(i);How much faster is this implementation than
Update 07/04/2018: added more clarifications to highlight the purpose of this test and added more details in the conclusion. Update 30/03/2018: the RxJava test has been updated to use Schedulers.computation() and all the tests for both RxJava and coroutines have been executed again. Thanks for all the comments that helped improve the comparison between the different implementations. I was curious
判断迷ってます。何か間違ってたら教えてください。 ライブラリにKotlinを使ってる場合、アプリ側に多少デメリットがあります。 アプリサイズKotlinを使ったライブラリを依存関係に追加すると、こんな感じにKotlinのランタイムのライブラリも入ってきます。 \--- project :libkotlin \--- org.jetbrains.kotlin:kotlin-stdlib-jre7:1.2.21 \--- org.jetbrains.kotlin:kotlin-stdlib:1.2.21 \--- org.jetbrains:annotations:13.0アプリ側がJavaの場合は、その分、単純にアプリサイズが増加します。 とは言え、ライブラリ自体そんなに大きくないので、すごく増えるということはなさそうです。 ココに書いてる通り、全部で約934KBで、Proguardを使うと
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く