Draft
Conversation
Collaborator
|
Why do we need to reverse the dependency between |
Member
Author
|
to use the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The interface and documentation of
linfa-hierarchicalis not updated in a long time. This PR adds the example to the documentation and changes the implementation oftransformtopredict, which is more correct in this context.Currently blocked on a cyclic dependency caused by implementing
linfa::Predictforlinfa::PredictRefwith kernel data. A workaround is by adding a feature flag tolinfa-kernelwhich removes alllinfarelated parts and including that into the dependency tree forlinfa.