I really enjoy these presentations where they dive into the decompiled dex and class files. Jetbrains and Google have clearly spent a bunch of time developing these tools which enable this feature, and it's not something I've really appreciated in the past.
Yes, in Android Studio 3.0 & 3.1 the Desugaring step is done by the Desugar tool that performs a form of transpilation. Usually that term is used for source-to-source compilation, in this case the source & output are different versions of java bytecode. In Android Studio 3.2 the desugaring step is done as part of the compilation from java bytecode to davlik byte code inside the D8 compiler.
![เปิดคำทำนาย นอสตราดามุส - บาบา วานก้า ปี 2025 คนทั่วโลกต้องเจออะไรบ้าง? | แฉ 11 ธ.ค. 67 [2/3] |GMM25](http://i.ytimg.com/vi/xmTIKWJUMPM/mqdefault.jpg)
I really enjoy these presentations where they dive into the decompiled dex and class files. Jetbrains and Google have clearly spent a bunch of time developing these tools which enable this feature, and it's not something I've really appreciated in the past.
Great talk! motivated me to look more into register vs stack based vm implementation..
Newest D8 and R8 are great :)
So desugaring is like transpilation?
Yes, in Android Studio 3.0 & 3.1 the Desugaring step is done by the Desugar tool that performs a form of transpilation. Usually that term is used for source-to-source compilation, in this case the source & output are different versions of java bytecode. In Android Studio 3.2 the desugaring step is done as part of the compilation from java bytecode to davlik byte code inside the D8 compiler.
Desugaring , is like removing all the cute coding tricks you do and turning it back to verbose jvm drama that it was originally lol
The other mentioned session about R8: th-cam.com/video/x9T5EYE-QWQ/w-d-xo.html
Great name.