Refer to "hooks" as "callbacks"?

[PaulRBerg]

In a recent internal discussion on Slack, @maxdesalle was confused about what exactly "callbacks" mean in the context of Sablier V2:

@andreivladbrg and I have been using the terms "hooks" and "callbacks" interchangeably. These terms refer to our V2 contracts' capacity to notify the senders and the recipients of streams when the other party makes a move (cancellation, renouncement, or withdrawal). For the callback to be triggered, the sender and the recipient must be a contract that implements one of the two following interfaces:

• ISablierV2LockupRecipient
• ISablierV2LockupSender

The question is: should we rename the hooks directory to callbacks? Alternatively, should we keep hooks but never refer to them as callbacks in our public outreach (marketing, documentation website, etc.)?

Both sound okay, but I see the value in having just one way we refer to this functionality.

Related:

• Hooks and reactivity #157
• ISablierV2Recipient: sender and recipient hooks #164

[PaulRBerg]

Let's stick with hooks.

"Callbacks" are a broader concept than "hooks", since the latter plays part in actualizing the former. A "callback" is the action of the protocol calling back the "hook" implemented by third-party developers.