NightOwl888 commented on issue #485: URL: https://github.com/apache/lucenenet/issues/485#issuecomment-833100893
It is difficult to imagine both maintaining a sweeping architecture change as well as keeping pace with Lucene's release schedule. It would presume that one of us has an advanced high-level understanding of the architecture to be able to make and then maintain such a change, but given that this is a low-level line-by-line port, it is not an understanding that anyone on the team has. Our focus is on keeping the project upgradable in the future to integrate new changes to Lucene, which unfortunately means that if we drift too far from the original source we would need a very detailed roadmap to follow to make each upgrade possible. I have to agree with @rclabo, [async/await is a pattern supported in Java](https://dzone.com/articles/async-await-in-java), so the best way to support it in .NET would be to lobby the [Lucene team](https://lucene.apache.org/core/discussion.html) to make the design changes at a high level first, which would be propagated to Lucene.NET when it is upgraded. In fact, I would make that argument about any significant high-level design change that isn't specifically made to address a gap between the platforms. And do it immediately, since Lucene is in the process of planning for version 9.0 right now. The only tool we have that helps us solve some of the failing tests is to run the code both in Java and in .NET to see where the paths diverge between the two. Once we lose the Java reference to work from, some bugs that are easy to identify now would effectively mean researching several high-level design concepts just to understand what the bug is before determining where it is, since we would be unable to distinguish between a bug that is due do to a difference between the Lucene behavior and the Lucene.NET behavior from a bug that was introduced in the new design. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
