Skip to content
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

[RFC]: Add/Update package of strided namespace for BooleanArray support (tracking issue) #2500

Closed
19 tasks done
Jaysukh-409 opened this issue Jul 3, 2024 · 2 comments
Closed
19 tasks done
Assignees
Labels
Tracking Issue Tracking issue.

Comments

@Jaysukh-409
Copy link
Member

Jaysukh-409 commented Jul 3, 2024

Description

This RFC proposes add or update all packages of strided namespace that needs to be changed in order to add BooleanArray support to Stdlib. The purpose of this issue is to serve as a tracking issue for update or add packages.

Packages need to added:

  • @stdlib/strided/base/reinterpret-boolean

Prerequisites of ndarray namespace:

  • @stdlib/ndarray/base/dtype-char
  • @stdlib/ndarray/base/dtype-desc
  • @stdlib/ndarray/base/dtype2c
  • @stdlib/ndarray/base/char2dtype
  • @stdlib/ndarray/safe-casts
  • @stdlib/ndarray/promotion-rules

Packages need to updated:

  • @stdlib/strided/dtypes
  • @stdlib/strided/base/nullary
  • @stdlib/strided/base/nullary-addon-dispatch
  • @stdlib/strided/base/unary
  • @stdlib/strided/base/unary-addon-dispatch
  • @stdlib/strided/base/mskunary
  • @stdlib/strided/base/mskunary-addon-dispatch
  • @stdlib/strided/base/binary
  • @stdlib/strided/base/binary-addon-dispatch

Related Issues

None

Questions

No.

Other

No.

Checklist

  • I have read and understood the Code of Conduct.
  • Searched for existing issues and pull requests.
  • The issue name begins with RFC:.
@stdlib-bot
Copy link
Contributor

👋 Hi there! 👋

And thank you for opening your first issue! We will get back to you shortly. 🏃 💨

@Jaysukh-409 Jaysukh-409 added the Tracking Issue Tracking issue. label Jul 3, 2024
@Jaysukh-409 Jaysukh-409 self-assigned this Jul 3, 2024
kgryte added a commit that referenced this issue Jul 4, 2024
PR-URL: #2508
Ref: #2500
Co-authored-by: Athan Reines <[email protected]>
Reviewed-by: Athan Reines <[email protected]>
kgryte added a commit that referenced this issue Jul 4, 2024
PR-URL: #2507
Ref: #2500
Co-authored-by: Athan Reines <[email protected]>
Reviewed-by: Athan Reines <[email protected]>
kgryte added a commit that referenced this issue Jul 4, 2024
PR-URL: #2505
Ref: #2500
Co-authored-by: Athan Reines <[email protected]>
Reviewed-by: Athan Reines <[email protected]>
kgryte added a commit that referenced this issue Jul 5, 2024
PR-URL: #2513
Ref: #2500
Co-authored-by: Athan Reines <[email protected]>
Reviewed-by: Athan Reines <[email protected]>
kgryte pushed a commit that referenced this issue Jul 6, 2024
kgryte pushed a commit that referenced this issue Jul 6, 2024
kgryte pushed a commit that referenced this issue Jul 6, 2024
kgryte pushed a commit that referenced this issue Jul 6, 2024
kgryte pushed a commit that referenced this issue Jul 6, 2024
kgryte pushed a commit that referenced this issue Jul 6, 2024
kgryte added a commit that referenced this issue Jul 6, 2024
PR-URL: #2525
Ref: #2500
Co-authored-by: Athan Reines <[email protected]>
Reviewed-by: Athan Reines <[email protected]>
kgryte pushed a commit that referenced this issue Jul 6, 2024
@kgryte
Copy link
Member

kgryte commented Jul 6, 2024

All tasks have now been completed. Closing...

@kgryte kgryte closed this as completed Jul 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Tracking Issue Tracking issue.
Projects
None yet
Development

No branches or pull requests

3 participants