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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding mongoose_subdomain_core #3116
adding mongoose_subdomain_core #3116
Changes from all commits
14b3e87
f5074dd
ee0f37f
1b81136
7f9f46e
ae7d6a0
f7f5b44
7ff708a
e8cb166
a4f9665
3e0a1a8
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The two types: record and map look a bit odd to me. I understand that the record is used for ETS operations and the map is easier to use in the tests but... I would only have the record here.
Applying the Occam's razor makes me think that having only one type here would have the following benefits:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't want to expose this record to the external code (not in this PR), it's not only about tests. I would say it was done not for the tests at all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not exposing the record beyond a a module would make more sense to me if there were a lot of data in the record taht we could hide. Otherwise it's just a lightweight and efficient data structure that you can just use directly instead of converting to a new structure that does not offer anything extra.
I don't want to start a long discussion here... it can stay as it is, in my view it's just unnecessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's keep it as it is for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can be a huge list in the process heap. I think we would not unregister subdomains during normal operation though.