Skip to content

Conversation

bremoran
Copy link
Contributor

This split means that the notional dependency tree from sockets looks like:

sockets
┣─ sal-td
┃ ┣─ sal
┃ ┗─ sal-stack-lwip
┃   ┣─ sal

(pruned for readability)

Since sal does not have a targetDependency on sal-stack-lwip, there is no circular dependency between the two. This means that a new sal can be published without breaking sal-stack-lwip.

@autopulated @0xc0170 @bogdanm

One module contains the SAL and the other contains target dependencies.
This eliminates definition-based circular dependencies from the SAL.
@bremoran
Copy link
Contributor Author

(This is a prototype and not expected to be merged for beta)

Don't panic, @bogdanm!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant