[GitHub] lucenenet issue #191: [WIP] Migrating Lucene.Net to .NET Core

2016-11-10 Thread synhershko
Github user synhershko commented on the issue: https://github.com/apache/lucenenet/pull/191 Thanks for the clarifications. Probably make sense to have it documented in code itself then :) --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] lucenenet issue #191: [WIP] Migrating Lucene.Net to .NET Core

2016-11-10 Thread NightOwl888
Github user NightOwl888 commented on the issue: https://github.com/apache/lucenenet/pull/191 > >There are 2 different PriorityQueue types in Lucene.Net > Is there a reason for this? Can we stay with one? Yes, there is a reason for that – that is the way it is

[GitHub] lucenenet issue #191: [WIP] Migrating Lucene.Net to .NET Core

2016-11-09 Thread synhershko
Github user synhershko commented on the issue: https://github.com/apache/lucenenet/pull/191 > AFAIK, the Support namespace is for pieces that need to be sourced from the JDK and/or close approximations to what is in the JDK that don't exist in the .NET framework. This is

[GitHub] lucenenet issue #191: [WIP] Migrating Lucene.Net to .NET Core

2016-11-02 Thread NightOwl888
Github user NightOwl888 commented on the issue: https://github.com/apache/lucenenet/pull/191 FYI - There are 2 branches that still need to be integrated before this is up to date with master: - https://github.com/NightOwl888/lucenenet/tree/core-tests -