```fun main() { var newList1 = listOf(listOf(1, "a", "b"), listOf(1, "a", "b"), listOf(1, "a", "...

# server

[andodeki]

fun main() {
    var newList1 = listOf(listOf(1, "a", "b"), listOf(1, "a", "b"), listOf(1, "a", "b"))
    var newList = listOf(1, "b", "C" to newList1)
    var defaultList = listOf(1, "a", 'B' to newList)

    var a = defaultList[2]

	print(a::class.java.typeName)  //kotlin.Pair
}
I need to access "newList1" but i cant since "defaultList" is a Pair
how can i access via index or how can i construct to get this behaviour

[nkiesel]

(a as Pair<Char, List<Any>>).second

[nkiesel]

of course, casts are evil. So hopefully your real code does have better typed and homogeneous data structures

[nkiesel]

btw: the correct channel for this would be #getting-started

[nkiesel]

and no, defaultList is not a Pair: it is a List<Any> (in you concrete example, a list consists of an Int, a String, and a Pair of Char and List) . Thus the "static" type of the list entries is Any (the supertype of all your item types), but individual items have different runtime types (which is why the cast is necessary)

[andodeki]

fun main() {
    data class Quote(
    	var int: Int,
        var item: String,
        var ItemList: Pair<String, List<Any>>
    )
    var newList1 = listOf(
        Quote(1, "asds dd", "sd dsdb" to emptyList()), 
        Quote(1, "adsd sdssdsds", "bsdds sdd" to emptyList()), 
        Quote(1, "asdsd sds", "bdsd sd" to emptyList())
    )
    var newList = listOf(
        Quote(1, "bsds sdsds", "Cdfdd fsd" to newList1)
    )
    var defaultList = listOf(
        Quote(1, "aasds ss", "Bdsf wsd" to newList)
    )

    var a = defaultList[0] //as Pair<Char, List<Any>>).second;

// 	print(a::class.java.typeName)
    print(a.ItemList::class.java.typeName) // kotlin.Pair
}

[andodeki]

still a kotlin.Pair i dont know why

[Richard Gomez]

What are you expecting? ItemList is kotlin.Pair because you've defined it as such:

var ItemList: Pair<String, List<Any>>.

[andodeki]

i got it now i need to use ".second" on the Pair to get the list

[Richard Gomez]

In general, that seems like a bad design for data. Why not have Map<String, List<Any>>?

[Matteo Mirk]

Don’t use Pair to model your data, it won’t add any semantic meaning to your code, quite the opposite, only confusion. Pair is handy for when you need to quickly return 2 values from a function or you need an intermediate structure in a functional pipeline.
Model your data structures using concepts and terms from the domain you need to model. Use the “Ubiquitous Language” as in Domain Driven Design.