now works with nvcc compiler#184
Conversation
|
Thanks for this PR! |
|
Hey, just checking up on this. I think all of your concerns have been addressed now @JohanMabille. |
|
Indeed, sorry for the late reply, I've been busy for the past few days. Let's merge this PR, next step is to upgrade to last implementation of variant. |
|
@JohanMabille are you a git submodule type of guy, or no (I've heard some dislike using them)? May make sense for mpark/variant. If so I'd totally make a PR for that. |
|
We usually consider git submodule as a terrible practice. The ideal approach would be to make mpark/variant a conda package and have |
This solves issue #183 and allows XTL to be used with host-side CUDA code. Previously, the nvcc compiler failed to correctly parse two LOC in XTL, and these expressions have been modified to something more friendly for nvcc. As a result of this, xtensor now also works with host-side CUDA!
I think adding a separate test for the nvcc compiler may not make sense at this point though.
Also... I hope I understood the rule on modifying the changelog correctly. Does each PR modify the changelog?