Skip to content

Issues: stdlib-js/metr-issue-tracker

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.

Sign up for GitHub

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

32 Open 10 Closed
32 Open 10 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

[RFC]: enable ESLint doctest linting for lib/index.js files 🤖 AI Allowed to use AI. difficulty: 2 May require some initial design or R&D, but should be straightforward to resolve and/or implement. Enhancement Task to enhance existing functionality. estimate: 4-8hrs Task which should take between 4 to 8 hours.
#41 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add complex dtype support to utils/named-typed-tuple difficulty: 3 Likely to be challenging but manageable. Enhancement Task to enhance existing functionality. estimate: >8hrs Task which is likely to take longer than 8 hours. ❌ No AI Not allowed to use AI.
#40 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add boolean dtype support to utils/named-typed-tuple 🤖 AI Allowed to use AI. difficulty: 3 Likely to be challenging but manageable. Enhancement Task to enhance existing functionality. estimate: >8hrs Task which is likely to take longer than 8 hours.
#39 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add missing typed array methods to utils/named-typed-tuple difficulty: 3 Likely to be challenging but manageable. estimate: >8hrs Task which is likely to take longer than 8 hours. Feature Task to add a new feature. ❌ No AI Not allowed to use AI.
#38 opened Feb 14, 2025 by kgryte
@headlessNode
[BUG]: add missing tests to utils/named-typed-tuple 🤖 AI Allowed to use AI. Bug Task to fix a bug. difficulty: 3 Likely to be challenging but manageable. estimate: >8hrs Task which is likely to take longer than 8 hours.
#37 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add string/base/slice-grapheme-clusters difficulty: 2 May require some initial design or R&D, but should be straightforward to resolve and/or implement. estimate: 2-4hrs Task which should take between 2 to 4 hours. Feature Task to add a new feature. ❌ No AI Not allowed to use AI.
#35 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add string/base/slice-code-points 🤖 AI Allowed to use AI. difficulty: 2 May require some initial design or R&D, but should be straightforward to resolve and/or implement. estimate: 2-4hrs Task which should take between 2 to 4 hours. Feature Task to add a new feature.
#34 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add string/base/slice difficulty: 1 Low degree of difficulty. Should be straightforward to implement and/or resolve. estimate: 2-4hrs Task which should take between 2 to 4 hours. Feature Task to add a new feature. ❌ No AI Not allowed to use AI.
#33 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add support to pre-push Git hook to run package tests after changing source files 🤖 AI Allowed to use AI. difficulty: 2 May require some initial design or R&D, but should be straightforward to resolve and/or implement. estimate: 2-4hrs Task which should take between 2 to 4 hours. Refactor Task to refactor existing code.
#32 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add stdlib REPL text lint rule to prevent name collisions with global identifiers difficulty: 3 Likely to be challenging but manageable. estimate: 4-8hrs Task which should take between 4 to 8 hours. Feature Task to add a new feature. ❌ No AI Not allowed to use AI.
#31 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add an ESLint rule to disallow BigInt literal syntax 🤖 AI Allowed to use AI. difficulty: 3 Likely to be challenging but manageable. estimate: 4-8hrs Task which should take between 4 to 8 hours. Feature Task to add a new feature.
#29 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add an ESLint rule which disallows new Array(...) difficulty: 2 May require some initial design or R&D, but should be straightforward to resolve and/or implement. estimate: 2-4hrs Task which should take between 2 to 4 hours. Feature Task to add a new feature. ❌ No AI Not allowed to use AI.
#28 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add blas/base/ggemm difficulty: 3 Likely to be challenging but manageable. estimate: 4-8hrs Task which should take between 4 to 8 hours. Feature Task to add a new feature. ❌ No AI Not allowed to use AI.
#27 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add accessor array support to blas/base/gnrm2 🤖 AI Allowed to use AI. difficulty: 2 May require some initial design or R&D, but should be straightforward to resolve and/or implement. estimate: <2hrs Task which should take less than 2 hours. Feature Task to add a new feature. Refactor Task to refactor existing code.
#26 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add accessor array support to blas/base/gaxpy difficulty: 2 May require some initial design or R&D, but should be straightforward to resolve and/or implement. estimate: <2hrs Task which should take less than 2 hours. Feature Task to add a new feature. ❌ No AI Not allowed to use AI. Refactor Task to refactor existing code.
#25 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add accessor array support to blas/base/gscal difficulty: 1 Low degree of difficulty. Should be straightforward to implement and/or resolve. estimate: <2hrs Task which should take less than 2 hours. Feature Task to add a new feature. ❌ No AI Not allowed to use AI. Refactor Task to refactor existing code.
#24 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add accessor array support to blas/base/gdot difficulty: 2 May require some initial design or R&D, but should be straightforward to resolve and/or implement. estimate: <2hrs Task which should take less than 2 hours. Feature Task to add a new feature. ❌ No AI Not allowed to use AI. Refactor Task to refactor existing code.
#23 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add accessor array support to blas/base/gasum 🤖 AI Allowed to use AI. difficulty: 1 Low degree of difficulty. Should be straightforward to implement and/or resolve. estimate: <2hrs Task which should take less than 2 hours. Feature Task to add a new feature. Refactor Task to refactor existing code.
#22 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add array/base/map difficulty: 2 May require some initial design or R&D, but should be straightforward to resolve and/or implement. estimate: 2-4hrs Task which should take between 2 to 4 hours. Feature Task to add a new feature. ❌ No AI Not allowed to use AI.
#21 opened Feb 14, 2025 by kgryte
1
@headlessNode
2
[RFC]: add array/base/reshape 🤖 AI Allowed to use AI. difficulty: 2 May require some initial design or R&D, but should be straightforward to resolve and/or implement. estimate: 2-4hrs Task which should take between 2 to 4 hours. Feature Task to add a new feature.
#20 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add array/base/linspace2d 🤖 AI Allowed to use AI. difficulty: 2 May require some initial design or R&D, but should be straightforward to resolve and/or implement. estimate: 2-4hrs Task which should take between 2 to 4 hours. Feature Task to add a new feature.
#19 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add array/base/count-ifs 🤖 AI Allowed to use AI. difficulty: 2 May require some initial design or R&D, but should be straightforward to resolve and/or implement. estimate: 2-4hrs Task which should take between 2 to 4 hours. Feature Task to add a new feature.
#18 opened Feb 14, 2025 by kgryte
@headlessNode
[BUG]: missing tests in ndarray/base/unary 🤖 AI Allowed to use AI. Bug Task to fix a bug. difficulty: 3 Likely to be challenging but manageable. estimate: 4-8hrs Task which should take between 4 to 8 hours.
#16 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add blas/ext/base/dmskrev difficulty: 2 May require some initial design or R&D, but should be straightforward to resolve and/or implement. estimate: 2-4hrs Task which should take between 2 to 4 hours. Feature Task to add a new feature. ❌ No AI Not allowed to use AI.
#15 opened Feb 14, 2025 by kgryte
@headlessNode
[RFC]: add array/base/pluck 🤖 AI Allowed to use AI. difficulty: 1 Low degree of difficulty. Should be straightforward to implement and/or resolve. estimate: 2-4hrs Task which should take between 2 to 4 hours. Feature Task to add a new feature.
#14 opened Feb 14, 2025 by kgryte
1
@headlessNode
2
ProTip! Mix and match filters to narrow down what you’re looking for.