Tracking issue for TryFrom/TryInto traits #33417

Activity

1. alexcrichton

   added

   B-RFC-approvedBlocker: Approved by a merged RFC but not yet implemented.Blocker: Approved by a merged RFC but not yet implemented.

   T-libs-api[DEPRECATED; DO NOT USE][DEPRECATED; DO NOT USE]

   on May 4, 2016
2. Manishearth

   added 3 commits that reference this issue on May 8, 2016

   Rollup merge of rust-lang#33426 - sfackler:try-from, r=aturon

   ...

   3f6d7c1

   Rollup merge of rust-lang#33426 - sfackler:try-from, r=aturon

   ...

   cc98f4c
3. Zoxc commented on May 9, 2016

   

   Zoxc

   on May 9, 2016

   Contributor

   More actions

   Is there a way to generically print an error with the original value if the conversion fails without requiring Clone so a related method which panics on failure could have nice error messages?

   👍React with 👍1Reacted by Solomon Ucko
4. chris-morgan commented on May 10, 2016

   

   chris-morgan

   on May 10, 2016

   Member

   More actions

   A discussion of whether this should go in the prelude is pending for when this goes stable.
5. alexcrichton

   added

   B-unstableBlocker: Implemented in the nightly compiler and unstable.Blocker: Implemented in the nightly compiler and unstable.

   and removed

   B-RFC-approvedBlocker: Approved by a merged RFC but not yet implemented.Blocker: Approved by a merged RFC but not yet implemented.

   on Jun 21, 2016
6. shepmaster commented on Jul 9, 2016

   

   shepmaster

   on Jul 9, 2016

   Member

   More actions

   Apologies if this is covered somewhere else, but what would we like to see before marking this as stable? I'm pretty sure I've reimplemented this functionality a few times in various projects, so a common reusable trait would make me 😄

   👍React with 👍16Reacted by Stanislav Tkach, Phil Ruffwind, Nicolas, Evgeniy Dushistov, Alexander Polakov, Richard Dodd, Clément Renault, remexre, Nikolai Vazquez, Daniel P. Clark and 6 more
7. sfackler

   added

   I-nominated

   on Jul 9, 2016
8. sfackler commented on Jul 9, 2016

   

   sfackler

   on Jul 9, 2016

   Member

   More actions

   We can bring it up for discussion for the next cycle.
9. 283 remaining items

   Load more

   Load more actions

10. SimonSapin commented on Mar 12, 2019

    

    SimonSapin

    on Mar 12, 2019

    Contributor

    More actions

    Oh I thought #58015 had landed, but it hasn’t yet… Let’s discuss it there.

    👍React with 👍2Reacted by Bart Smykla and Ahmad Rifa'i

    😄React with 😄2Reacted by ૮༼⚆︿⚆༽つ and Ahmad Rifa'i
11. bors

    added a commit that references this issue on Mar 12, 2019

    Auto merge of #58015 - icefoxen:tryfrom-docs, r=SimonSapin

    ...

    7c19e1e
12. o01eg commented on Mar 30, 2019

    

    o01eg

    on Mar 30, 2019

    Contributor

    More actions

    Could TryFrom trait have a method to check if argument could be converted without consuming it?

    fn check(value: &T) -> bool

    👎React with 👎6Reacted by Jake Goulding, RustyYato, Clar Fon, Steven Roose, Nate Kent and Flux Xu
13. Kerollmops commented on Mar 30, 2019

    

    Kerollmops

    on Mar 30, 2019

    Contributor

    More actions

    One way to work with non-consuming impossible conversion could be to return the consumed non-convertible value along with the associated error.

    👍React with 👍5Reacted by icefoxen, Clar Fon, Kai Giebeler, Flux Xu and Ellen Emilia Anna Zscheile
14. SimonSapin commented on Apr 9, 2019

    

    SimonSapin

    on Apr 9, 2019

    Contributor

    More actions

    Oops this should have been closed by #58302. Closing now.

    ---

    @o01eg The typical way to do non-consuming conversion is to implement e.g. TryFrom<&'_ Foo> instead of TryFrom<Foo>.
15. SimonSapin

    closed this as completedon Apr 9, 2019
16. ErichDonGubler commented on Apr 9, 2019

    

    ErichDonGubler

    on Apr 9, 2019

    Contributor

    More actions

    Wait...this shouldn't actually close until landing on stable Thursday, right?
17. sfackler commented on Apr 9, 2019

    

    sfackler

    on Apr 9, 2019

    Member

    More actions

    No, we close tracking issues when the PR stabilizing the feature lands on master.

    👀React with 👀1Reacted by Jake Goulding
18. SimonSapin commented on Apr 9, 2019

    

    SimonSapin

    on Apr 9, 2019

    Contributor

    More actions

    No, we usually close tracking issue when the stabilization or removal lands in the master branch. After that there is nothing left to track. (Unless a newly-reported bug comes up, but we handle that separately.)

    👍React with 👍1Reacted by kennytm

    👀React with 👀1Reacted by Jake Goulding
19. jethrogb commented on Apr 9, 2019

    

    jethrogb

    on Apr 9, 2019

    Contributor

    More actions

    Tracking issues are closed by the PR that stabilizes them. Depending on the release cycle, this could be up to 12 weeks before stable is released.

    👀React with 👀1Reacted by Jake Goulding
20. ErichDonGubler commented on Apr 9, 2019

    

    ErichDonGubler

    on Apr 9, 2019

    Contributor

    More actions

    Got it. Thanks for the clarification, everyone! :)

    😄React with 😄1Reacted by Jake Goulding
21. shepmaster commented on Jun 5, 2019

    

    shepmaster

    on Jun 5, 2019

    Member

    More actions

    @gregdegruy update your version of Rust to 1.34 or higher.

    👍React with 👍1Reacted by greg
22. bors

    added a commit that references this issue on Oct 1, 2019

    Merge #327

    ...

    9b7eefb
23. daniel-ferguson

    added a commit that references this issue on Feb 7, 2020

    Add nom [1] dependency

    ...

    119bed1
24. eddyb

    added a commit that references this issue on Nov 14, 2022

    Stabilize the TryFrom and TryInto traits

    ...

    75bc5af