-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Hide much of Microsoft.ML.Model namespace. #2649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2649 +/- ##
=========================================
Coverage ? 71.54%
=========================================
Files ? 801
Lines ? 141840
Branches ? 16119
=========================================
Hits ? 101474
Misses ? 35916
Partials ? 4450
|
test/Microsoft.ML.CodeAnalyzer.Tests/Resources/ContractsCheckResource.cs
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're not wrong in the sense that this file should be addressed, but I might prefer to address this and similar matter in work more appropriate to that task. If it was just one line I'd probably opportunistically fix it, but this file needs some work. Seems related to #1973. Edit: Looks like this was mostly already the subject of a PR by @artidoro ! |
@@ -239,7 +239,7 @@ public static class TransformerChain | |||
{ | |||
public const string LoaderSignature = "TransformerChain"; | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this can be made internal. We usually do that with the LoaderSignature
elsewhere. #Closed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -239,7 +239,7 @@ public static class TransformerChain | |||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that I think about it, I suspect that this entire class can be made internal. We should expose these methods in MLContext
if we need them, and they are not there yet. Please let me know if I am wrong. #Closed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's all fine, but, maybe we could internalize things unrelated to the issue and this PR in subsequent PRs? My goal @artidoro is not to internalize the entire assembly in one go, just some specific types and infrastructure I see in the Microsoft.ML.Model
namespace, as described in the issue, title of the PR, and so on. Perhaps we could evaluate the worth of the PR along those dimensions? #Resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So to be clear, I don't really intend to do this. Unless I literally can't get a signoff any other way. #Resolved
Maybe. This however is not the subject of this PR. Just to remind you, the title of PR is "Hide much of Microsoft.ML.Model namespace", which does not include this. I anticipate that in other PRs as we are finalizing parts of our API surface, you will find people touching files that themselves require internalization work. In reply to: 465776776 [](ancestors = 465776776) Refers to: src/Microsoft.ML.Data/DataLoadSave/TransformerChain.cs:203 in 888be1f. [](commit_id = 888be1f, deletion_comment = False) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixes #2640. Per usual commits are logically ordered to reflect the natural order in which structures are internalized, etc.