Skip to content
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.

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

Plan for CLI11 1.8 #270

Closed
henryiii opened this issue Apr 28, 2019 · 4 comments · Fixed by #280
Closed

Plan for CLI11 1.8 #270

henryiii opened this issue Apr 28, 2019 · 4 comments · Fixed by #280

Comments

@henryiii
Copy link
Collaborator

henryiii commented Apr 28, 2019

Here's my plan for 1.8, and a rough idea for the future.

The last major feature for 1.8 (#242) was merged. In the next week or so, I'd like to do a little polishing (feel free to pitch in and test/suggest/help). I'm hoping to look at #250 and #253 in that time. Possibly also add a move constructor to simplify a common use case #268 (if it does not appear to be safe, I'll be happy to wait till 1.9 to decide, though). I'll probably try to make an official beta release (pretty much consider it in beta now if you'd like to test it!), and a full release at some point not long after.

For 1.9, I'd like to work on a method to allow part of the library to be precompiled to address #194. I'll also be removing and adding some warnings for the deprecated bits of the library, preparing for a slightly bigger removal in 2.0. I'm also highly considering dropping support for GCC 4.7 in one of those versions; please speak up if you need it!

Other general tasks include moving more of the CI over to Azure (I plan to release a post on the process on iscinumpy.gitlab.io, too), moving the tutorial so it shares the same repository (I love gitlab.io, but it will be easier to keep in sync with the code and additions - and maybe CLI11 will be synced there too!)

@phlptp
Copy link
Collaborator

phlptp commented Apr 30, 2019

@henryiii for the ExtraArguments error when using the move version of parse, can you check to make sure the excess arguments get printed in proper order for the different parse calls with extra arguments. I looked at it but it might be printing backwards in some cases, and I think someone else needs to take a look at it.

@phlptp
Copy link
Collaborator

phlptp commented Apr 30, 2019

I have a few tweaks related to issue #260, particular the footer callback, but I am still tinkering with it yet, so I won't submit any related PR's until after 1.8 is released.

@henryiii
Copy link
Collaborator Author

Besides checking the move version of parse, is there anything left for 1.8?

@phlptp
Copy link
Collaborator

phlptp commented May 15, 2019

There is the PR #253 that is open with an issue with gcc 4.7 So I guess that could be fixed or wait until after 1.8 and gcc 4.7 is dropped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants