spierce703/17/2018, 9:46 PM
olonho03/18/2018, 9:12 AM
spierce703/18/2018, 9:33 PM
The current api has it's own merits, but being able to declare a data class as
frozen data class SharedData(val string: String, val int: Int, val member: SharedDataMember)
/ immutable would be a nice addition as well. Are there downsides to building it into the class definition in addition to the approach currently implemented? What is the plan to integrate this with common projects so that we can write common code that works properly with kotlin/native's threading model, and in Java / JS as well?
msink03/19/2018, 12:25 AM
already exists and means exactly that - immutability.
olonho03/19/2018, 7:20 AM
msink03/19/2018, 8:47 AM
classes can be placed in read-only memory, and without reference countiong.
olonho03/19/2018, 11:17 AM
spierce703/19/2018, 1:09 PM
olonho03/19/2018, 1:24 PM
spierce703/19/2018, 1:55 PM