Skip to content

Office Hours (2026-05-26)聽#126

Closed
Closed

Description

@github-actions

馃専 Join Us for Weekly Office Hours! 馃専

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.

Everyone is welcome鈥攄rop in and say hello!

Time

UTC Tue 26-May-2026 16:30 (04:30 PM):

Timezone Date/Time
US / Pacific Tue 26-May-2026 09:30 (09:30 AM)
US / Mountain Tue 26-May-2026 10:30 (10:30 AM)
US / Central Tue 26-May-2026 11:30 (11:30 AM)
US / Eastern Tue 26-May-2026 12:30 (12:30 PM)
EU / Western Tue 26-May-2026 17:30 (05:30 PM)
EU / Central Tue 26-May-2026 18:30 (06:30 PM)
EU / Eastern Tue 26-May-2026 19:30 (07:30 PM)
Moscow Tue 26-May-2026 19:30 (07:30 PM)
Chennai Tue 26-May-2026 22:00 (10:00 PM)
Hangzhou Wed 27-May-2026 00:30 (12:30 AM)
Tokyo Wed 27-May-2026 01:30 (01:30 AM)
Sydney Wed 27-May-2026 02:30 (02:30 AM)

or in your local time:

Links

Joining the meeting

Agenda

  • Have specific things to discuss? Please comment in the issue thread below to add specific items to the agenda.

Activity

  1. added
    Office HoursIssue announcing office hours and soliciting associated agenda items.
    on May 19, 2026
  2. officiallyanee commented on May 26, 2026

    @officiallyanee
    Member

    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 )

  3. nakul-krishnakumar commented on May 26, 2026

    @nakul-krishnakumar
    Member

    I want to discuss about the following:

    1. 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
    2. Continuing our discussion in the GSoC meet, can I refer dindex-of-row? Also is order necessary for dkmeans-init-plus-plus too?
    3. Designing ml/strided/dkmeans-init-plus-plus API GOT CLARIFIED IN THE GSOC MEET 鉁旓笍
    4. 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?
  4. prajjwalbajpai commented on May 26, 2026

    @prajjwalbajpai
    Member
    • I need some guidance on getting the test coverage to 100% for this routine.
    • Continuing with the above PR, how to structure the test files for routines where there are too many tests.
  5. nirmaljb commented on May 26, 2026

    @nirmaljb

    This has been cleaned and just needs a final look: stdlib-js/stdlib#11989

  6. Shanwis commented on May 26, 2026

    @Shanwis

    Could stdlib-js/stdlib#12253 be reviewed? This updates the normal MGF benchmarks/examples to include negative valid inputs.

  7. gunjjoshi commented on May 26, 2026

    @gunjjoshi
    Member

    I wanted to discuss about:

  8. nirmaljb commented on May 26, 2026

    @nirmaljb

    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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Office HoursIssue announcing office hours and soliciting associated agenda items.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions