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

WIP: Roadmap document for standard library #561

Closed
wants to merge 9 commits into from
Closed

Conversation

joehendrix
Copy link
Contributor

This is a draft document that describes desired features in the standard library.

I thought I'd submit it as a PR to the repo itself for now for feedback, but I am not sure if that's the best long term home.

Feedback appreciated.

docs/Roadmap.md Outdated Show resolved Hide resolved
docs/Roadmap.md Outdated Show resolved Hide resolved
docs/Roadmap.md Outdated Show resolved Hide resolved
docs/Roadmap.md Outdated Show resolved Hide resolved
docs/Roadmap.md Outdated Show resolved Hide resolved
docs/Roadmap.md Outdated Show resolved Hide resolved
docs/Roadmap.md Outdated Show resolved Hide resolved
joehendrix and others added 6 commits January 26, 2024 00:12
Co-authored-by: François G. Dorais <[email protected]>
Co-authored-by: François G. Dorais <[email protected]>
Co-authored-by: François G. Dorais <[email protected]>
Co-authored-by: François G. Dorais <[email protected]>
Co-authored-by: François G. Dorais <[email protected]>
Co-authored-by: François G. Dorais <[email protected]>
@hargoniX
Copy link
Collaborator

This sounds like an awesome vision! I'm particularly looking forward to the IO part so we can start writing proper applications in Lean as well!

One thing that I was wondering about: Do we maybe want to roughly describe what we believe does not fit in std but instead in other libraries? Or is it too early to make such a cut-off in your opinion?

@fgdorais
Copy link
Collaborator

I thought a bit about the "long-term home" issue. I think it would be weird if the home was outside Std itself, upstream docs could just link to the Std doc. (Which folder is debatable velocipede housing :-) I'm thinking that's the best way for now and also long term. I don't see additional value in centralizing such documentation but I am always happy to be enlightened by opposing arguments.

Aside: There should be a doc (or similar name) label for this and similar PRs.

@joehendrix
Copy link
Contributor Author

One thing that I was wondering about: Do we maybe want to roughly describe what we believe does not fit in std but instead in other libraries? Or is it too early to make such a cut-off in your opinion?

I definitely think more detail is warranted and will be working on that. I don't want to speak for other libraries, but I think more guidance will help contributors.

@joehendrix joehendrix added awaiting-review This PR is ready for review; the author thinks it is ready to be merged. awaiting-author Waiting for PR author to address issues and removed awaiting-review This PR is ready for review; the author thinks it is ready to be merged. labels Feb 1, 2024
Co-authored-by: François G. Dorais <[email protected]>
docs/Roadmap.md Outdated Show resolved Hide resolved
Co-authored-by: François G. Dorais <[email protected]>
@kim-em kim-em closed this Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-author Waiting for PR author to address issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants