For example, I have and interface with

fun get(count: Int = 20): List<Item>

. I call

impl.get()

and I want to know that I expect 20 items.

With reflection? You probably have to give out some more information, or I can’t help you…

I think it's easier to introduce a constant 🙂

Most likely if you control the source 🙂

if you are writing the interface, include a constant and use that as the default instead of an integer literal

If I have a

Map<String, List<Event>>

and I want to flatmap that into one straight list of objects, what is the easiest way to do so?

I know there's a .flatMap method but I can't figure out how to make it work, and the documentation's clear that it needs a transformation but I don't know what I should use and I can't find a good example on the googles.

I want this because I'm trying to make a sectioned recyclerview, if that helps.

Hello, I have some questions about the newly shipped 1.1.0-beta version. There is a great feature that you can use a

getter

method to define the type of variables:

val myString get() = "hi"

However, when I use

var myString get() = “hi”

, I got an error message “Property must be initialized”, I think it should work on both

val

and

var

.

Yet another question is bought by this feature, when I define properties like this:

var str1 = “Hi”
val str2 get() = str1

When the str1 is changed, then str2 is changed, so this means

val

can not keep the value of str2 immutable?

@adam-mcneilly Actually even simpler:

flatMap {it -> it}

Hmm but that doesn't keep track of the strings anymore. Any way of getting ["a", 1, 2, "b", 3, 4, 5]? It feels hacky to me, too, but I'm not sure of any better way to handle a sectioned recyclerview. Given a position, I need to know if it's a section header, or an event item, and I thought the simplest way to do that would be to bump it into a list and switch based on object type

Ah you want the keys too

Yeah. If I'm going in the wrong direction with this solution I'll welcome suggestions too but that was the best I could think up.

I ended up just doing something like this because it's late and I want to get this hackathon project working

This will give you a

Collection<Any>

, not exactly easy to handle

@User uploaded a file: Untitled

where full list is just

List<Any>

Yeah you don't want that

Didn't think so haha

Whatever you want to do with this map, you're probably better off just doing it on

map.entries

So I guess here's the issue. I want to populate a list, and my adapter gives me a position. Given a position, how do I know if it's supposed to be a section header or it's one of the list items? Given that, I just realized that I also might move this to a linked map so I can make sure the sections are in the right order

You haven't given enough information between the generic code above and your specific "data section" problem for me to make a connection between the two problems

The view is displaying a list of events, and I want them to be sectioned by date. So we'll have a view that says Friday, followed by the rows with Friday's events, then a row that reads "saturday", followed by its events, and so on. The data structure I'm currently storying this in is

Map<String, List<Event>>

so I have each day and its events in their own bucket. I know Friday is index 0, because it's the first key. Friday's first event would be index 1, and so on down the line. What I'm having trouble with is recreating this logic programatically. I don't want to have to walk my way from key -> values, key -> values each time to reach my position. Is that more clear?

The keys are the days?

yeah. Again, I am open to suggestions if you're thinking I'm approaching the wrong way, but that seemed to make the most sense to me, because I want a row with the day name to behave like a section header between them.

I don't see why you need a map, why not

class Display(day: String, events: List<Event>>)

and a list of those?