Add gb.MAX_SIZE
, which is GrB_INDEX_MAX + 1
#519
Merged
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.
INDEX_MAX
may be a nice global value to expose. The GraphBLAS spec doesn't have many of these globals.This is the largest index value, not the size of the domain of indices. For example, create the largest vector via
Vector(int, INDEX_MAX + 1)
. Also, note that the spec does not specify a value forGrB_INDEX_MAX
, only that implementations define it, so it may be backend-dependent.Alternatively, we could instead define
MAX_SIZE
, which would beGrB_INDEX_MAX + 1
. I think this is much more natural to use; e.g.,Matrix(int, MAX_SIZE, MAX_SIZE)
. I don't think we need bothINDEX_MAX
andMAX_SIZE
.So, which to y'all prefer,
INDEX_MAX
orMAX_SIZE
? Feel free to suggest different names too.CC @michelp @jim22k @SultanOrazbayev