retrolambda

Is there a way to disable warning about Jack is required to support java 8 language features. while using Retrolambda? I don't want jack support for now since it doesn't yet compile our project. loadjang android studio Add below codes in your application gradle after that do synck // ----- add buildscript { repositories { mavenCentral() } dependencies { classpath 'me.tatarka:gradle-retrolambda:3.2.4' } } repositories { mavenCentral() } // ----- end apply plugin: 'com.android.application' apply plugin: 'me.tatarka.retrolambda' // ----- add android { compileSdkVersion 23 buildToolsVersion "23.0

I am using Java 8 in my Android project. I have setup both Jack (In android application module) and Retrolambda (in other modules). The problem I am having is that my Lambda expressions crash in one specific scenario when I try to make it use class variable (and I can reproduce it in any module), in all others situations it works as expected. Maybe this is a standard Java behaviour, but I couldn't find any explanations so far. Would anyone know where the problem is? My class and crash below: public class LambdaBugTest { private final String parentClassVariableString =

I want to run 2 asynchronous tasks, one followed by the other (sequentially). I have read something about ZIP or Flat, but I didn't understand it very well... My purpose is to load the data from a Local SQLite, and when it finishes, it calls the query to the server (remote). Can someone suggests me, a way to achieve that? This is the RxJava Observable skeleton that I am using (single task): // RxJava Observable Observable.OnSubscribe<Object> onSubscribe = subscriber -> { try { // Do the query or long task... subscriber.onNext(object); subscriber.onCompleted(); } catch (Exception e) {

We know that anonymous classes maintain a reference to their enclosing instance and that this can lead to context leaks on Android. Since retrolambda backports lambdas to Java7, it could be worth a try. It seems that Java8 lambdas do not have this problem, but I can't find any official information on that. Any clue? Hamed Moghaddam Here is some info. From the following link http://cr.openjdk.java.net/~briangoetz/lambda/lambda-state-final.html : This has a beneficial implication for memory management: while inner class instances always hold a strong reference to their enclosing instance,