since method references can be as debug-friendly as lambda expressions, perhaps they should be?

mark.yagnatinsky at barclays.com mark.yagnatinsky at barclays.com
Mon Aug 16 21:41:12 UTC 2021


> It's a fun hack, and i don't think anyone want such horror in the real implementation.
Is it fixable, or is there likely no non-hacky way to do this?

> There is also an issue if in the future we want to use a ldc constant dynamic instead of invokedynamic in the generated code because in that case, the lambda proxy will be shared in between two method references
That sounds like an argument to just not do that then, just as we don't optimize tail calls today for partly the same reason: to keep stack traces more readable.

Or not so simple?

_________________________________________________________________________________________________________________________________________________________________________________________________________________________________
“This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer.

For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer regarding market commentary from Barclays Sales and/or Trading, who are active market participants; https://www.investmentbank.barclays.com/disclosures/barclays-global-markets-disclosures.html regarding our standard terms for the Investment Bank of Barclays where we trade with you in principal-to-principal wholesale markets transactions; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com.”  
_________________________________________________________________________________________________________________________________________________________________________________________________________________________________
If you are incorporated or operating in Australia, please see https://www.home.barclays/disclosures/importantapacdisclosures.html for important disclosure.
_________________________________________________________________________________________________________________________________________________________________________________________________________________________________
How we use personal information  see our privacy notice https://www.investmentbank.barclays.com/disclosures/personalinformationuse.html 
_________________________________________________________________________________________________________________________________________________________________________________________________________________________________


More information about the jdk-dev mailing list