[
https://issues.apache.org/jira/browse/LUCENENET-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118932#comment-13118932
]
Prescott Nasser commented on LUCENENET-446:
-------------------------------------------
Additionally, all shifting is broken (this causes an infinite loop in parts of
the code - specifically the parts that write to file store (affectively making
this patch useless in it's current form).
The problem is that uint is not CLS compliant, and updating it to CLS Complaint
(Int64) breaks shifting. Normally a -1 as a uint, would be 4Billion etc,
however as an Int64, it is still -1. This means that we would have to adjust
nearly all of the code relating to shifting, which is above my knowledge at the
moment. Even making these changes would in my head reset our current status of
having a relatively battle tested 2.9.4 release ready to go.
Further, the fact that we can't fix a few of the mentioned items above
(scoreDocs vs ScoreDocs, etc) we cannot make 2.9.4 CLS compliant without
breaking the public api.
With these issues, I think we should abandon the idea of making 2.9.4 CLS
Compliant.
> Make Lucene.Net CLS Compliant
> -----------------------------
>
> Key: LUCENENET-446
> URL: https://issues.apache.org/jira/browse/LUCENENET-446
> Project: Lucene.Net
> Issue Type: Task
> Components: Lucene.Net Core
> Affects Versions: Lucene.Net 2.9.4
> Reporter: Prescott Nasser
> Attachments: Lucene2.9.4-CLS-partial-fix
>
>
> Make Lucene.Net CLS Compliant
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
