[
https://issues.apache.org/jira/browse/LUCENE-10074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17406125#comment-17406125
]
Dawid Weiss commented on LUCENE-10074:
--------------------------------------
Oh, I don't think it matters that much at runtime. I just wanted to check if
javac would optimize this away (similar to how it treats string constants
concatenation, for example). I understand javac-developers though: it doesn't
make much sense to do such optimizations at javac-side given how much complex
code reshuffling is going on at runtime (c2 in particular).
> Remove unneeded default value assignment
> ----------------------------------------
>
> Key: LUCENE-10074
> URL: https://issues.apache.org/jira/browse/LUCENE-10074
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Zach Chen
> Priority: Minor
>
> This is a spin-off issue from discussion here
> [https://github.com/apache/lucene/pull/128#discussion_r695669643,] where we
> would like to see if there's any automatic checking mechanism (ecj ?) that
> can be enabled to detect and warn about unneeded default value assignments in
> future changes, as well as in the existing code.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
