[
https://issues.apache.org/jira/browse/LUCENENET-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237015#comment-13237015
]
Christopher Currens commented on LUCENENET-446:
-----------------------------------------------
I was looking at this again, and we can be CLSCompliant and leave all of that
FieldsWriter shifting alone.
Being CLS compliant only applies to public and protected members. We can do
whatever we want with internal or private members, including using non-CLS
compliant types. On top of there being a lot of methods marked public that
should be internal or protected internal, I think this might be easier than we
originally thought.
> 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
> Fix For: Lucene.Net 3.0.3
>
> 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
