kitttn
04/16/2017, 10:58 AMsomeList[:]
in Pythonjoachim.reiss.
04/16/2017, 12:56 PMcedric
04/16/2017, 2:40 PMequals()
and hashCode()
are not methods where you want to do that. Guava has some helper methods, though: https://gist.github.com/rocketraman/1399080/a50ea2206f6ea4bda65ef00d1f54aab6d654d3bdjw
04/16/2017, 6:59 PMlet
and when
on different lines which there's no reason to docodeslubber
04/16/2017, 11:18 PMgroostav
04/17/2017, 3:45 AMcedric
04/17/2017, 3:46 AMTBD: link to sonatype/maven centralBuild with Kobalt and upload to JCenter in just two lines in your build file 😄
gbaldeck
04/17/2017, 2:18 PMamiracam
04/17/2017, 4:21 PMrobstoll
04/17/2017, 5:22 PMIan
04/17/2017, 10:37 PMvar s : String? = null
exec {
s = createS()
}
s!!.doSomething()
the exec
block is executed synchronously so s
will be assigned to a non-null value, but the type system doesn’t know this hence the !!
. createS()
can only be called within the exec
block.
Obviously the !!
is ugly, I’m trying to figure out whether there is a better way to get s
“out” of the inner code block. I could modify exec
such that it will return whatever is returned by the code block, but what if I need to get multiple variables out of the code block?senthilkumarv
04/18/2017, 11:33 AMorangy
sreich
04/18/2017, 12:31 PMjlleitschuh
04/18/2017, 2:37 PMjava.util.function.Function
has an apply
method. How can I tell the kotlin compiler to call the apply
method and not the extension function?spierce7
04/18/2017, 3:51 PMblah blah
is never used." Is there a way to silence that specific Kotlin warning for my entire team? We're using gradle to build.john.kennedy
04/18/2017, 4:50 PMmwerschy
04/18/2017, 9:34 PMpcarrier
04/19/2017, 12:29 AMredrield
04/19/2017, 3:21 AMbamdmux
04/19/2017, 6:03 AMmiha-x64
04/19/2017, 9:08 AMmg6maciej
04/19/2017, 9:36 AMAdapter
tho. Prefer to have each case as a class.mg6maciej
04/19/2017, 9:39 AMsnowe
04/19/2017, 5:02 PMchriswayoub
04/20/2017, 4:40 AMilya.chernikov
04/20/2017, 9:22 AMkotlin.compiler.execution.strategy
to in-process
to disable it. (The prop should be visible by kotlin gradle plugin, so I guess you can do it via GRADLE_OPTS
env var, but it depends on the gradle execution settings.)
But it would be nice to understand the problem first, so could you please first set the prop -Dkotlin.daemon.verbose
and rerun the gradle build with --debug
, and then send us the relevant part of the log/output (that would be last several hundreds lines starting from the failing module compilation). We’ll appreciate that a lot.
// cc: @alexey.tsvetkovkevinrob
04/20/2017, 9:54 AMeviltak
04/20/2017, 2:32 PMcedric
04/20/2017, 2:53 PMkotlinc
directrly (or K2JVMCompiler
) or is that daemon only usable from Gradle?