Fix C FFI extension after moving TH to C++ #5005
Merged
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
added 2 commits
February 1, 2018 21:59
soumith
approved these changes
Feb 2, 2018
Contributor
Author
|
gcc 4.8 CI will pass after we merge pytorch/extension-ffi#16. |
Contributor
|
@pytorchbot retest this please |
ezyang
approved these changes
Feb 2, 2018
| } THGenerator; | ||
| typedef struct THGenerator THGenerator; | ||
|
|
||
| typedef struct THGeneratorState THGeneratorState; |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
aten/src/TH/THGenerator.h
Outdated
| THGeneratorState gen_state; | ||
| }; | ||
|
|
||
| #endif No newline at end of file |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This fixes the issue mentioned in #4041.