From 367ba05c85b76542d0b59ad4a996cd6a3884594b Mon Sep 17 00:00:00 2001 From: Abhi Date: Fri, 8 Nov 2024 12:02:54 +0530 Subject: [PATCH] remove un-necessary para --- src/routes/instructions/invoke-custom.svelte | 31 -------------------- 1 file changed, 31 deletions(-) diff --git a/src/routes/instructions/invoke-custom.svelte b/src/routes/instructions/invoke-custom.svelte index c937100..554077b 100644 --- a/src/routes/instructions/invoke-custom.svelte +++ b/src/routes/instructions/invoke-custom.svelte @@ -252,37 +252,6 @@ MethodHandle. Read more about it here

-

- Lambdas and invoke-custom -

-

- In Java bytecode, lambda expressions usually get implemented through - something called the LambdaMetafactory, - which can create a functional interface at runtime. -

-

- In Android’s Dalvik bytecode, even though invoke-custom can - support dynamic calls similar to Java’s invokedynamic, - standard lambdas don’t typically get compiled into - invoke-custom. Instead, they are often translated into - anonymous inner classes(like if you do in an android - project they get converted to synthetic subclasses) - or something similar in the DEX files. -

-

- When invoke-custom is Actually Used -

-

invoke-custom is intended for scenarios that need:

-
    -
  1. - Dynamic method resolution through a - call site. -
  2. -
  3. - Special handling by a bootstrap method that isn’t just simple - functional interface invocation. -
  4. -

References