use i64::MAX instead of 0x3f3f3f3f3f3f3f3f #22
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.
seems more rusty to use built-in constants
it seems that 0x3f3f... is used in competitive programming because...
i64
. However it doesn't seem to matter here.include <numeric_limits>
and usestd::numeric_limits<int64_t>::max()
. But in rusti64::MAX
is easier to type.memset(..., 0x3f, ...)
tricks. But here we are initializing withvec![Self::INF; self.graph.num_v()]
which should have compiler optimizations anyway.tests seem to pass...