Populate $callers field for callback functions #397
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The same way Task does it: https://hexdocs.pm/elixir/Task.html#module-ancestor-and-caller-tracking This makes it easier to track requests across processes.
|
Hi @legoscia! What exactly is your intent with this? What would you use the callers for? The issue is that the caller is not going to necessarily be a process you own; I don't want to have to commit to maintaining that contract... Maybe some examples of how this would be useful would help me understand. Specifically I mean why you would need to track the caller of a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The same way Task does it:
https://hexdocs.pm/elixir/Task.html#module-ancestor-and-caller-tracking
This makes it easier to track requests across processes.