so it has to do with the variance characteristic of

List

?

What is the idiomatic way of cloning a mutableMap? I have one called translations and I am copying it in the following way which looks wrong to me but it does work

translations.map { it.key to it.value }.toMap()

@hackerham We've implemented the new suspend function convention Lool at https://github.com/Kotlin/kotlin-coroutines/issues/71 And it's mainly incompatible with the old one

oh

#coroutines 🚓

is that NoClassDefFoundError known bug?

i haven’t seen it for a while (not since moving to 1.0.5, at least). i don’t remember exactly how to reproduce the error but you might be able to track it down quicker by temporarily creating

package error; class NoClassDefFoundError

somewhere in your project (don’t commit it, though!) when i did that i got some useful error messages showing me exactly what i did wrong.

might’ve been an error in my imports, not sure

I have a question about how infix methods would behave syntactically inside of a receiver lambda

I have some code like this

@User uploaded a file: Untitled

addExisting is defined as an infix method, and I wanted to remove the this in front

but when I do, it bombs

is something like what I'm wanting to do even possible?

@User uploaded a file: Untitled and commented: this is what I would like to do

You can make an extension function instead

but you'll have to add parentheses

why isn't

dynamic

available for JVM?

I am now dealing with a large c# codebase that uses dynamic extensively. Its a nightmare. I'm glad the JVM doesn't support it.

You can't even debug dynamics to see what the heck they are.

first, there's no reason not to be able to see what it is in JVM debugger

(If my frustration is showing through, I've just spent more than an hour trying unsuccessfully to figure out the right calls to make on a dynamic var)

second, it can be useful in some contexts for objects that change their method list, if nothing else

I'm sure it's useful in some contexts. The problem is that people will start using it when they shouldn't, because its seductively easy.

although I believe it would be better to implement a base class notation for dynamic

so something like

val properties: dynamic Map<String, String> = ...

meaning that the object has to be a subtype of Map, has specific return types for

get

or

contains

or other Map methods, but also supports invocations on methods not declared in Map

Forgive my ignorance, but

dynamic

is new to me in my one week of experience with c#. What is the use case for that which is not possible by subclassing

Map

?

Apparently the existence of dynamic in c# was for interop with other languages that don't have a notion of types.

let's say I want to add property access syntax to map, a la groovy, so that map.key == map["key"]. there's no way to call that method with type checking enabled. there are other use cases for it though, specifically in DSL/scripting, but that's the idea

Why

a

is unresolved when I’m trying to define

b

object here? (I created SO question: https://stackoverflow.com/questions/40923418/why-i-cannot-reference-constructor-arguments-inside-of-the-class-when-defining-o)