-
Notifications
You must be signed in to change notification settings - Fork 3k
inets: add type specifications #6661
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
inets: add type specifications #6661
Conversation
CT Test Results 2 files 21 suites 12m 18s ⏱️ For more details on these failures, see this check. Results for commit 8cf960c. ♻️ This comment has been updated with latest results. To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass. See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally. Artifacts// Erlang/OTP Github Action Bot |
c996ada to
7b8bda2
Compare
|
This has been stalled a bit, but I plan on fixing all related issues this week :) |
346730f to
8ae46eb
Compare
8ae46eb to
c38f8bc
Compare
Updates records, function headers, etc so that the `inets` app can be type checked by type checkers such as eqWAlizer.
0c5dcc0 to
8cf960c
Compare
This PR adds some type specifications to the
inetsmodule.These have been checked by Dialyzer and eqWAlizer.
Note: Not all types have been added because that would require bigger changes in
stdlib, but the ones that were possible have been added and are type checked by eqWalizer. The ones that are not possible usually refer to prop lists, because the return type in the spec is alwaysterm(), which makes eqWAlizer to think thatterm()is the input type to another function. When this other function expects (e.g.,)integer(), it reports a mismatch betweenterm()andinteger().