jkbbwr
10/28/2018, 12:18 AMfun fopen(path: String, mode: String): File {
contract {
mustBeClosed()
}
}
René
10/28/2018, 6:15 AMHamza
10/29/2018, 8:20 AMmuralimohan962
10/29/2018, 8:30 AMlouiscad
10/29/2018, 9:15 AMPaul Woitaschek
10/29/2018, 9:22 AMThomas Legrand
10/29/2018, 10:43 AMmzgreen
10/29/2018, 11:30 AMclass Foo {
private val test: String
init {
test = "test"
}
}
and this doesn’t:
class Foo {
private val test: String
init {
bar()
}
private fun bar() {
test = "test"
}
}
Is there any valid case why it may fail? Or it’s the compiler’s fault that it doesn’t recognize bar
is called inside an init
?Jan Vomlel
10/29/2018, 11:34 AMIcaro Temponi
10/29/2018, 12:43 PMdavid-wg2
10/29/2018, 12:50 PMorangy
10/29/2018, 2:56 PMenleur
10/29/2018, 3:20 PMorangy
10/29/2018, 3:32 PMksinkar
10/29/2018, 3:32 PMHamza
10/29/2018, 3:35 PMIcaro Temponi
10/29/2018, 3:37 PModay
10/29/2018, 3:37 PMHamza
10/29/2018, 3:38 PMOussama Haff.
10/29/2018, 3:38 PMMarc Knaup
10/29/2018, 3:39 PMbuildSrc
?luke_c
10/29/2018, 4:14 PMjlleitschuh
10/29/2018, 4:22 PMdave08
10/29/2018, 4:33 PMjlleitschuh
10/29/2018, 4:34 PMRandom
which is awesome!
I'm wondering why there wasn't an official Kotlin version of SecureRandom
added.
Without an official SecureRandom
100% kotlin based crypto libraries can't be implemented without adding platform specific implementations.
Dan Kaminsky did an interesting talk at defcon about why more standard libraries libraries should offer SecureRandom
by default. So many software security bugs have been caused purely because someone on the implementation side goofed and used a predictable Random number generator.
https://youtu.be/xneBjc8z0DE▾
Hele
10/29/2018, 5:00 PMelect
10/29/2018, 5:32 PMjlleitschuh
10/29/2018, 6:25 PMnfrankel
10/29/2018, 6:52 PMnfrankel
10/29/2018, 6:53 PMnfrankel
10/29/2018, 6:53 PMjuancho
12/28/2018, 3:50 PM