You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have questions about stdlib? Need help fixing a bug, figuring out what to do next, or just looking for feedback? Join our weekly office hours to connect with project maintainers, stay updated on the latest project news, and chat with other community members. This is a great opportunity to ask questions, share ideas, and engage directly with the stdlib team.
Where should doc rules be placed? Athan's comment about it during gsoc - essentially to not put in the doc block itself as they will likely be used in future to source into HTML source doc and we will need to introduce post-processing to remove them. A problem: it鈥檚 fine for a single rule but there are multiple potential rules we might end up requiring depending on how many use cases we wish to support instead of outright skipping.
For example ( with ref to what type of rule rust uses ),
compile_fail - A rule that says the given example block should not compile.
It could be useful in cases of (...) placeholders which are present at places with a large number of input parameters.
standalone_crate tag - this is useful when we successfully make the doctest for single example blocks and move towards merging them together to improve performance. In our use case, at least all the example blocks of a single package can be merged together.
I think a way to go about would be to look more into functionality to ignore certain tags while creating the rendered document.
SO, I just wanted to know what is the future plan to render these documents, if any?
( if it will be done through Doxygen then it provides a way to ignore specific things and similarly could be found for other ways )
In ml/strided/dkmeans-init-plus-plus API, the trials var is expected to be >= 1. How should I handle this in the implementation? Should I expect the user to pass in a valid trials? Should I raise an error or return NaN on trials < 1? Ref: ml/incr/kmeans/lib/init_kmeansplusplus.js
Continuing our discussion in the GSoC meet, can I refer dindex-of-row? Also is order necessary for dkmeans-init-plus-plus too?
Designing ml/strided/dkmeans-init-plus-plus APIGOT CLARIFIED IN THE GSOC MEET 鉁旓笍
How to benchmark ml/strided/dkmeans-init-plus-plus?GOT CLARIFIED IN THE GSOC MEET 鉁旓笍
Should I benchmark it like the rest of the strided packages by only varying len? or should I benchmark it on different values of other variables too, like k, M, N and trials?
Any similar benchmarks I can refer to? Can I refer to either ml/incr/kmeans or PR #2819?
Activity
officiallyanee commentedon May 26, 2026
Where should doc rules be placed?
Athan's comment about it during gsoc - essentially to not put in the doc block itself as they will likely be used in future to source into HTML source doc and we will need to introduce post-processing to remove them.
A problem: it鈥檚 fine for a single rule but there are multiple potential rules we might end up requiring depending on how many use cases we wish to support instead of outright skipping.
For example ( with ref to what type of rule rust uses ),
compile_fail- A rule that says the given example block should not compile.It could be useful in cases of (...) placeholders which are present at places with a large number of input parameters.
standalone_crate tag- this is useful when we successfully make the doctest for single example blocks and move towards merging them together to improve performance. In our use case, at least all the example blocks of a single package can be merged together.I think a way to go about would be to look more into functionality to ignore certain tags while creating the rendered document.
SO, I just wanted to know what is the future plan to render these documents, if any?
( if it will be done through Doxygen then it provides a way to ignore specific things and similarly could be found for other ways )
nakul-krishnakumar commentedon May 26, 2026
I want to discuss about the following:
ml/strided/dkmeans-init-plus-plusAPI, thetrialsvar is expected to be >= 1. How should I handle this in the implementation? Should I expect the user to pass in a valid trials? Should I raise an error or return NaN on trials < 1? Ref:ml/incr/kmeans/lib/init_kmeansplusplus.jsordernecessary fordkmeans-init-plus-plustoo?DesigningGOT CLARIFIED IN THE GSOC MEET 鉁旓笍ml/strided/dkmeans-init-plus-plusAPIHow to benchmarkGOT CLARIFIED IN THE GSOC MEET 鉁旓笍ml/strided/dkmeans-init-plus-plus?len? or should I benchmark it on different values of other variables too, likek,M,Nandtrials?ml/incr/kmeansor PR #2819?prajjwalbajpai commentedon May 26, 2026
nirmaljb commentedon May 26, 2026
This has been cleaned and just needs a final look: stdlib-js/stdlib#11989
Shanwis commentedon May 26, 2026
Could stdlib-js/stdlib#12253 be reviewed? This updates the normal MGF benchmarks/examples to include negative valid inputs.
gunjjoshi commentedon May 26, 2026
I wanted to discuss about:
rfftf, and the corresponding tests? Ref: feat: addfft/base/fftpack/rfftf聽stdlib#12002 (comment) ?@stdlib/assert/is-almost-same-float64array, or should we have an explicitforloop withisAlmostSameValue? Ref: feat: addfft/base/fftpack/rfftf聽stdlib#12002 (comment)nirmaljb commentedon May 26, 2026
Just a quick question left: what is the reference used for
math/base/special/truncn?https://github.com/stdlib-js/stdlib/blob/develop/lib/node_modules/%40stdlib/math/base/special/truncn/lib/main.js