-
Notifications
You must be signed in to change notification settings - Fork 839
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
chore: add docs, part of #37 #6433
Conversation
- add pragma `#![warn(missing_docs)]` to the following - `arrow-array` - `arrow-cast` - `arrow-csv` - `arrow-data` - `arrow-json` - `arrow-ord` - `arrow-pyarrow-integration-testing` - `arrow-row` - `arrow-schema` - `arrow-select` - `arrow-string` - `arrow` - `parquet_derive` - add docs to those that generated lint warnings - Remove `bitflags` workaround in `arrow-schema` At some point, a change in `bitflags v2.3.0` had started generating lint warnings in `arrow-schema`, This was handled using a [workaround](apache#4233) [Issue](bitflags/bitflags#356) `bitflags v2.3.1` fixed the issue hence the workaround is no longer needed.
c2f93d3
to
feb6d17
Compare
@alamb for your perusal. |
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.
Other than the one comment about safety this PR is amazing. Thank you @ByteBaker
Updated the PR. |
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.
Thank you @ByteBaker
🚀 |
Thanks again |
add pragma
#![warn(missing_docs)]
to the followingarrow-array
arrow-cast
arrow-csv
arrow-data
arrow-json
arrow-ord
arrow-pyarrow-integration-testing
arrow-row
arrow-schema
arrow-select
arrow-string
arrow
parquet_derive
add docs to those that generated lint warnings
Remove
bitflags
workaround inarrow-schema
. At some point, a change inbitflags v2.3.0
had started generating lint warnings inarrow-schema
. This was handled using a workaround. Here is the original issue.bitflags v2.3.1
fixed the issue hence the workaround is no longer needed.