8000 Community driven roadmap · Issue #600 · doctest/doctest · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Community driven roadmap #600

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.

Sign up for GitHub

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

Jump to bottom
Open
5 tasks
Saalvage opened this issue Jan 23, 2022 · 4 comments
Open
5 tasks

Community driven roadmap #600

Saalvage opened this issue Jan 23, 2022 · 4 comments

Comments

@Saalvage
Copy link
Member
Saalvage commented Jan 23, 2022 •
edited
Loading

I think that instead of focusing on interesting features or those that would look good on the box, doctest should instead focus on implementing features that people actually using doctest would benefit from on a frequent basis.
This is why I'm moving the roadmap into this issue, where everyone will be able to comment their thoughts!
This should mostly be a place to share rough ideas that are not concrete enough to justify an issue of their own and in general discuss the future development of doctest.

2.5:

  • Clean up all the docs, benchmarks and whatnot
  • Splitting the two monolithic doctest files up into more managable chunks (while keeping it single header for release)
  • Generic container and STL stringification
  • CaseInvariant string comparison utility
  • Look into the feature of String. Full fledged lightweight std::string alternative (with more tests!), or removal in favor of it?

Stuff I will never get to but it would probably make sense to take a look at at some point:
@Saalvage Saalvage mentioned this issue Jan 23, 2022
Closed
@Saalvage Saalvage pinned this issue Jan 23, 2022
@Saalvage Saalvage mentioned this issue Jan 23, 2022
Closed
@wendajiang
Copy link

Can #685 be add to the roadmap?

@fran6co
Copy link
fran6co commented Dec 8, 2022

This one is really important so we can test crash dumping and other situations -> #326

@jokervTv
Copy link
Contributor

Is there any information about MPI here?

@cdeln cdeln mentioned this issue Aug 16, 2024
Open
@USwampertor
Copy link

Are there any plans for microbenchmarking such as Catch2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@fran6co @wendajiang @Saalvage @jokervTv @USwampertor
0