Use explicit potential function

[elazarg]

Avoid using template for array-like access

Summary by CodeRabbit

• New Features

  • Introduced a more flexible approach for handling potential functions in graph operations, allowing any callable type to be used.
  • Enhanced methods for managing graph operations, improving their functionality and maintainability.

• Bug Fixes

  • Improved error handling for potential overflows during data type conversions, ensuring robustness.

• Documentation

  • Updated comments and formatting for better readability and clarity.

• Refactor

  • Updated type alias for Weight in the SplitDBM class to enhance clarity and consistency.

[coderabbitai]

Actionable comments posted: 3

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Reviewing files that changed from the base of the PR and between bc91973 and a1331aa.

📒 Files selected for processing (2)

• src/crab/split_dbm.cpp (6 hunks)
• src/crab_utils/graph_ops.hpp (15 hunks)

[coveralls]

coverage: 89.556% (-0.02%) from 89.578%
when pulling 7a3bce0 on potential-function
into bc91973 on main.