Skip to content

Use atty crate in libtest instead of rolling our own #80937

Closed as not planned
Closed as not planned

Description

@camelid

cc #80888
cc @jyn514

This issue has been assigned to @mattwilkinsonn via this comment.

Activity

  1. added
    A-libtestArea: `#[test]` / the `test` library
    C-cleanupCategory: PRs that clean code up or issues documenting cleanup.
    E-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
    T-libsRelevant to the library team, which will review and decide on the PR/issue.
    on Jan 12, 2021
  2. jyn514 commented on Jan 12, 2021

    @jyn514
    Member

    @camelid what happened to #42732 (comment) ?

  3. nagisa commented on Jan 12, 2021

    @nagisa
    Member

    winapi has since been improved to no longer imply long build times at the very least.

  4. camelid commented on Jan 12, 2021

    @camelid
    MemberAuthor

    But I think we should probably use atty since it's so widely used.

  5. artorias111 commented on Jan 23, 2021

    @artorias111

    Hey! Is this a good issue if I'm just getting used to contribute to various projects. Not really familiar with the rust codebase but would like to try if I can contribute.

  6. jyn514 commented on Jan 23, 2021

    @jyn514
    Member

    @artorias111 yes, this would be a good first issue I think. I'm not 100% convinced we should make the change, but the implementation is easy, just add atty as a dependency and use it in libtest: #80897 (comment)

  7. artorias111 commented on Jan 23, 2021

    @artorias111

    @jyn514 sure, I'll give it a try then

  8. diohabara commented on Oct 20, 2021

    @diohabara

    @jyn514
    Those participated do not seem to be working on this issue, and the related PR is also inactive.
    So, can I assign this task to myself?

  9. diohabara commented on Oct 20, 2021

    @diohabara

    I'll do it for now, but please let me know if you have any problems.

  10. diohabara commented on Oct 20, 2021

    @diohabara

    @rustbot claim

  11. vramana commented on Mar 25, 2022

    @vramana
    Contributor

    @diohabara Are you still interested to work on this? Or can I claim it?

  12. jyn514 commented on Mar 25, 2022

    @jyn514
    Member

    #91121 is making good progress; I don't think it makes sense to duplicate work.

  13. camelid commented on Mar 25, 2022

    @camelid
    MemberAuthor
  14. self-assigned this
    on Mar 25, 2022
  15. joshtriplett commented on Oct 15, 2022

    @joshtriplett
    Member

    #98033 just merged.

  16. saethlin commented on Oct 21, 2022

    @saethlin
    Member

    @joshtriplett Should this have been closed by #98033?

  17. ChrisDenton commented on Oct 22, 2022

    @ChrisDenton
    Member

    I believe so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

A-libtestArea: `#[test]` / the `test` libraryC-cleanupCategory: PRs that clean code up or issues documenting cleanup.E-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.T-libsRelevant to the library team, which will review and decide on the PR/issue.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions