Channels
#stdlib
- m
masted
03/08/2016, 12:56 PM@mikehearn: point of view, for me it's looks like usual notation of set theory, so it's easy readable, again, for me - v
voddan
03/08/2016, 1:03 PMbreak the contract of
not sure the contract is applicable to Kotlin
by throwingcompareTo - v
voddan
03/08/2016, 1:04 PMand an exception is to be expected if you compare different hierarchies - v
voddan
03/08/2016, 1:05 PMbtw, the idea is not mine and the code is not mine. I just really liked the possibility for a clean unambiguous syntax - d
dalexander
03/08/2016, 1:09 PMI think operators throwing exceptions is generally unintuitive. It's an interesting idea though. - n
natpryce
03/08/2016, 1:56 PMCould it be enforced at compile time? - n
natpryce
03/08/2016, 1:57 PME.g.Copy codeoperator fun <T, U:T> Klass<T>.compareTo(u: Klass<U>) = 1 operator fun <U, T:U> Klass<T>.compareTo(u:Klass<U>) = -1 - k
kirillrakhman
03/08/2016, 1:57 PMyou could restrict the generic type parameter of
but generally , you don't know themKClass - k
kirillrakhman
03/08/2016, 1:58 PMif you already know them, you don't need to compare them - e
eshioji
03/08/2016, 3:07 PMDo you guys think it would be appropriate to add a few enum related methods to stdlib.collections? Like
? Seems like a reasonable thing to add, but AFAIK it’s not there yetenumMapOf - c
cbruegg
03/08/2016, 3:14 PMWhat does your hypothetical enumMapOf do? - e
eshioji
03/08/2016, 3:24 PMSomething like - e
eshioji
03/08/2016, 3:24 PM-.scala - d
damian
03/08/2016, 3:28 PMHow is that better than making the cold/warm as properties on the enum values?Copy codeenum class Direction(val temperature: String? = null) { NORTH("cold"), SOUTH("warm"), WEST(), EAST(); } - d
damian
03/08/2016, 3:29 PMI can see the advantage of a mapping in the other direction (to look up enum values based on strings) - e
eshioji
03/08/2016, 3:30 PMI mean, there’s definitely a use case forEnumMap - d
dalexander
03/08/2016, 3:30 PMHow is that different from
?mapOf(<enumval1> to <val1>, <enumval2> to <val2>) - j
jw
03/08/2016, 3:30 PM
is more efficient (just likeEnumMap
)EnumSet - e
eshioji
03/08/2016, 3:31 PMI believe mapOf won’t return an EnumMap implementation - e
eshioji
03/08/2016, 3:31 PMeven if the keys are enums - j
jw
03/08/2016, 3:31 PMthese sound just like new overloads - d
dalexander
03/08/2016, 3:31 PMAh, thanks for the clarification. - e
eshioji
03/08/2016, 3:32 PMI’d think it’s close to methods like
andlinkedMapOf
etchashMapOf - e
eshioji
03/08/2016, 4:17 PMOne complication is that unlike other
methods,*MapOf
would have to have access to the enum’s class object. So either we can use the signatureenumMapOf
and disallow creating a empty enum map (because we won’t be able to get hold of the class object), or we could require the user to pass the class object as a parameter.enumMapOf(pairs) - j
jw
03/08/2016, 4:22 PMnot a problem with a reified type - e
eshioji
03/08/2016, 4:23 PMoh do we have reified type? - j
jw
03/08/2016, 4:23 PMwe have inlining which fakes reified types... - e
eshioji
03/08/2016, 4:23 PMoh ok, didn’t know that - j
jw
03/08/2016, 4:25 PMCopy codeinline fun <reified K : Enum<K>, V> enumMapOf(vararg pairs: Pair<K, V>): EnumMap<K, V> { val map = EnumMap<K, V>(K::class.java) pairs.forEach { map.put(it.first, it.second) } return map } - e
eshioji
03/08/2016, 4:26 PMoh sweet