8000 Bring pyarray and pytensor up to date with xtensor 0.20.0 by yungyuc · Pull Request #192 · xtensor-stack/xtensor-python · GitHub
[go: up one dir, main page]

Skip to content

Bring pyarray and pytensor up to date with xtensor 0.20.0 #192

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

Merged

Conversation

yungyuc
Copy link
Contributor
@yungyuc yungyuc commented Mar 22, 2019

In xtensor-stack/xtensor@bfa8879 , 3 type aliases introduced to xcontainer_inner_types specialization:

  • using reference = typename storage_type::reference;
  • using const_reference = typename storage_type::const_reference;
  • using size_type = typename storage_type::size_type;

They should be added to xtensor-python to keep it working for xtensor 0.20.0.

In xtensor-stack/xtensor@bfa8879 , 3 type aliases introduced to xcontainer_inner_types specialization:

* using reference = typename storage_type::reference;
* using const_reference = typename storage_type::const_reference;
* using size_type = typename storage_type::size_type;

They should be added to xtensor-python to keep it working for xtensor 0.20.0.
@JohanMabille
Copy link
Member

Thanks for this fix!

@wolfv
Copy link
Member
wolfv commented Mar 22, 2019

awesome!

@SylvainCorlay SylvainCorlay merged commit 4d0b4ff into xtensor-stack:master Mar 22, 2019
@yungyuc yungyuc deleted the update-for-xtensor-0.20.0 branch March 22, 2019 10:31
@yungyuc
Copy link
Contributor Author
yungyuc commented Mar 22, 2019

Thanks a lot for accepting this.

@SylvainCorlay
Copy link
Member

Thank you for contributing. we will be pushing out releases very soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0