Fix to accept chainer.Variable collection input #79
Conversation
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
disktnk
force-pushed
the
fix/variable-input
branch
from
671c1a7 to
ef6890b
Compare
disktnk
changed the title
|
Let's get this merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
By #65 , current exporter does not accept
chainer.Variablecollection such as tuple like(chainer.Variable, chainer.Variable), and this PR fixes it along with adding tests (fixes #75)This issue is found on chainer-compiler's test, for example gen_mnist_mlp.py, however, this PR resolve the failure partially (ref #80). I will fix it another PR later.