Skip to content
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

ELLPACK matrix format #1

Closed
5 tasks done
gflegar opened this issue Feb 7, 2018 · 2 comments · Fixed by #10
Closed
5 tasks done

ELLPACK matrix format #1

gflegar opened this issue Feb 7, 2018 · 2 comments · Fixed by #10
Assignees
Labels
is:new-feature A request or implementation of a feature that does not exist yet.

Comments

@gflegar
Copy link
Member

gflegar commented Feb 7, 2018

  • declare gko::matrix::Ell class template in core/matrix/ell.hpp
  • implement any device independent methods in core/matrix/ell.cpp
  • mark device dependent methods (like apply) as NOT_IMPLEMENTED
  • add unit tests for device independent methods in core/test/matrix/ell.cpp
  • add your names to contributors.txt 😄
@gflegar gflegar mentioned this issue Feb 7, 2018
7 tasks
@gflegar gflegar added the is:new-feature A request or implementation of a feature that does not exist yet. label Feb 7, 2018
@yanjen
Copy link
Collaborator

yanjen commented Feb 8, 2018

Dear Professor Goran,
I called a pull request from a branch and accidentally created a new one #10
What is the right way to do this?

@gflegar
Copy link
Member Author

gflegar commented Feb 8, 2018

@yanjen you did everything correctly! No need to change anything as far as opening the pull request is concerned. This is an issue (where you discuss what's supposed to be done), and #10 is a pull request (where you present the code once you've done it). To be honest, I have no idea why github shares the counter between issues and pull requests, and I too find it a bit confusing (gitlab has separate counters for example).

You can however "link" the issue to the pull request and have it automatically closed when the PR is merged, as explained here: https://github.com/blog/1506-closing-issues-via-pull-requests

@yanjen yanjen mentioned this issue Feb 8, 2018
greole added a commit that referenced this issue Sep 11, 2021
* add prefixed macro definition

* Data validation macro generalisation fix windows (#2)

* check if linebreak causes windows build to break

* check if linebreak causes windows build to break

* check if empty macro arg causes windows build to break

* test if removing VA_ARGS resolves msvc error

* test PASS_ON hack

* Add missing PASS_ON

* Add tests for complex values is_finite tests

* Refactor macro expansion macro

* Test if PASS_ON is needed when calling GKO_APPLY_MACRO

* Refactor CALL_AND_RETURN_IF_CASTABLE macro

* Moves GKO_CALL_FOR_... macros to types.hpp
greole added a commit that referenced this issue Sep 27, 2021
* add prefixed macro definition

* Data validation macro generalisation fix windows (#2)

* check if linebreak causes windows build to break

* check if linebreak causes windows build to break

* check if empty macro arg causes windows build to break

* test if removing VA_ARGS resolves msvc error

* test PASS_ON hack

* Add missing PASS_ON

* Add tests for complex values is_finite tests

* Refactor macro expansion macro

* Test if PASS_ON is needed when calling GKO_APPLY_MACRO

* Refactor CALL_AND_RETURN_IF_CASTABLE macro

* Moves GKO_CALL_FOR_... macros to types.hpp
greole added a commit that referenced this issue Oct 15, 2021
* add prefixed macro definition

* Data validation macro generalisation fix windows (#2)

* check if linebreak causes windows build to break

* check if linebreak causes windows build to break

* check if empty macro arg causes windows build to break

* test if removing VA_ARGS resolves msvc error

* test PASS_ON hack

* Add missing PASS_ON

* Add tests for complex values is_finite tests

* Refactor macro expansion macro

* Test if PASS_ON is needed when calling GKO_APPLY_MACRO

* Refactor CALL_AND_RETURN_IF_CASTABLE macro

* Moves GKO_CALL_FOR_... macros to types.hpp
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is:new-feature A request or implementation of a feature that does not exist yet.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants