📚 What?
{talib} is to be implemented in {ledgr} and the structure there have raised an important point (See issue blechturm/ledgr#2): Pre-calculating lookback periods for relevant indicators.
Implementing this makes sense and aligns with the core idea that {talib} should be easily adaptable for downstream implementation. The current implementation checks for lookback validity and returns an error via C if invalid. A separate lookback function that returns a <logical> could help downstream packages with error catching and custom error messages.
The key question is whether the function should be exported, or not. The API is already enormous, and adding lookback functions just for the possibility of someone taking dependency is too much.
📚 What?
{talib} is to be implemented in {ledgr} and the structure there have raised an important point (See issue blechturm/ledgr#2): Pre-calculating lookback periods for relevant indicators.
Implementing this makes sense and aligns with the core idea that {talib} should be easily adaptable for downstream implementation. The current implementation checks for lookback validity and returns an error via C if invalid. A separate lookback function that returns a
<logical>could help downstream packages with error catching and custom error messages.The key question is whether the function should be exported, or not. The API is already enormous, and adding lookback functions just for the possibility of someone taking dependency is too much.