horus.app: Add erts
to application dependencies
#15
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.
Why
Horus relies on the availability of
erts
to initialize the list of modules to skip when it needs to decide if a call should be followed to extract a function or if the call should be preserved as is.It already depends on
kernel
andstdlib
for instance. I assumed thaterts
was implicit as I don't see how Erlang can work without it. It looks like iferts
is not included explicitly in an Erlang release file or in the applications it bundles, it is excluded from the release (theerts
Erlang application, not the actual runtime). This breaks Horus because it won't know about e.g. theerlang
module and will try and fail to extract functions from that module.Fixes #14.