Skip to content

std.optparse: please backport fixes from optparse package or remove from std #110

Open

Description

@ngie-eign

I recently ran into a bug fixed in optparse v1.4 since a prototype program I wrote had used - in an option description.
Please either update the module from the optparse project or remove the module on the stable release to prevent others from tripping over bugs similar to the one I did.

Activity

  1. changed the title [-]std.optparse: please backport fixes from `optparse` package or remove[/-] [+]`std.optparse`: please backport fixes from `optparse` package or remove from `std`[/+] on Sep 23, 2026
  2. gvvaughan commented on Oct 11, 2026

    @gvvaughan
    Contributor

    I've stalled on a multi-year project to split the lua-stdlib grab-bag of assorted unrelated batteries into a suite of smaller focussed libraries. The focussed libraries are more or less in good shape:

    But there's not a clear home for std.tree, and maybe some other small outliers.

    And lua-stdlib itself is effectively on life-support. The blocker is that lua-stdlib underpins a substantial stack of other modules and programs, and the focussed libraries while much cleaner and (IMHO) better designed are not entirely compatible.

    What's left: tearing out the guts of lua-stdlib, making it depend on all of the focussed libraries, and then coding all the shims to make projects that depend on all of lua-stdlib get a fully backwards compatible API.

  3. gvvaughan commented on Oct 11, 2026

    @gvvaughan
    Contributor

    @ngie-eign what is the bug you encountered exactly, and what is it that you need back porting and to where? I'll be happy to merge your PR if you know what needs fixing. Otherwise please give me a reproducer for your bug and I'll look into it when I get some time.

    Note that unreleased lua-stdlib has already dropped std.optparse, but top-of-tree is not backwards compatible with the last release.

  4. ngie-eign commented on Oct 12, 2026

    @ngie-eign
    Author

    4. @ngie-eign what is the bug you encountered exactly, and what is it that you need back porting and to where? I'll be happy to merge your PR if you know what needs fixing. Otherwise please give me a reproducer for your bug and I'll look into it when I get some time.
    Note that unreleased lua-stdlib has already dropped std.optparse, but top-of-tree is not backwards compatible with the last release.

    There’s a single bug fix in the release I mentioned 🙂. If that could be backported to the stdlib copy, that would fix the hang I ran into with dashes in my usage string. Alternatively, if it’s just nuked, that would work for me (and no action would be required, minus putting out a new release).

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions