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
{{ message }}
Repository navigation
std.optparse: please backport fixes from optparse package or remove from std #110
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.
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
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.
@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 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).
Activity
[-]std.optparse: please backport fixes from `optparse` package or remove[/-][+]`std.optparse`: please backport fixes from `optparse` package or remove from `std`[/+]gvvaughan commentedon Oct 11, 2026
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.
gvvaughan commentedon Oct 11, 2026
@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.ngie-eign commentedon Oct 12, 2026
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).