replace the method names with cryptic punctuation sequences. Words are typically easier
to read than punctuation and easier to find documentation on, even if they’re somewhat
longer.
More concise code takes less time to write and, more important, less time to read.
This improves your productivity and lets you get things done faster.
1.4.3 Safe
In general, when we speak of a programming language as safe, we mean its design
prevents certain kinds of errors in a program. Of course, this isn’t an absolute quality; no
language prevents all possible errors. In addition, preventing errors usually comes at a
cost. You need to give the compiler more information about the intended operation of the
program, so the compiler can then verify that the information matches what the program
does. Because of that, there’s always a trade-off between the level of safety you get and
the loss of productivity required to put in more detailed annotations.
With Kotlin, we’ve attempted to achieve a higher level of safety than in Java, with a
smaller overall cost. Running on the JVM already provides a lot of safety guarantees: for
example, memory safety, preventing buffer overflows, and other problems caused by
incorrect use of dynamically allocated memory. As a statically typed language on the
JVM, Kotlin also ensures the type safety of your applications. This comes at a smaller
cost than with Java: you don’t have to specify all the type declarations, because in many
cases the compiler infers the types automatically.
Kotlin also goes beyond that, meaning more errors can be prevented by checks at
compile time instead of failing at runtime. Most important, Kotlin strives to remove the
NullPointerException
from your program. Kotlin’s type system tracks values that can
and can’t be null and forbids operations that can lead to a NullPointerException at
runtime. The additional cost required for this is minimal: marking a type as nullable takes
only a single character, a question mark at the end:
May be null
May not be null
In addition, Kotlin provides many convenient ways to handle nullable data. This helps
greatly in eliminating application crashes.
Another type of exception that Kotlin helps avoid is the ClassCastException. It
happens when you cast an object to a type without first checking that it has the right type.
In Java, developers often leave out the check, because the type name must be repeated in
val s: String? = null
val s2: String = ""
剩余362页未读，继续阅读
renlei413326889
- 粉丝: 13
- 资源: 27
我的内容管理
展开
最新资源
- Vue实现iOS原生Picker组件：详细解析与实现思路
- Arduino蓝牙小车：参数调试与功能控制
- 百度Java面试精华：200页精选资源涵盖核心知识点
- Swift使用CoreData填坑指南：CoreData在Swift 3.0的变化
- 微距离无线充电器创新设计及其实验探索
- MTK Android平台开发全攻略：44步详解流程
- RecyclerView全面解析：替代ListView的新选择
- Android开发：自动适配中英文键盘解决方案
- Android调用WebService接口教程
- Android开发：BitmapUtil图片处理全解析与实例
- Android多线程断点续传实现详解
- PCA算法在人脸识别会议签到系统中的应用
- EventBus 3.0：Android事件总线详解与实战应用
- Android FileUtil：全面解析文件操作实用技巧与实例
- RecyclerView添加头部和尾部实战教程
- Android实现微博滑动固定顶部栏实战与优化
资源上传下载、课程学习等过程中有任何疑问或建议，欢迎提出宝贵意见哦~我们会及时处理！
点击此处反馈
