Login
You're viewing the discuss.systems public feed.
  • Leonardo Giovanni Scurkroltan@functional.cafe
    Jul 28, 2026, 2:34 AM

    @aDot Why is #1 regrettable?

    I can see #2 being awkward if you're doing const generics maybe though I never tried it?

    #3 is awkward because of the in-place mutation, I think?

    #4 isn't a trait, but I think you're referring to the whole Pin/Unpin shitshow?

    💬 1🔄 0⭐ 0

Replies

  • laundlaund@wetdry.world
    Jul 28, 2026, 7:40 AM

    @kroltan @aDot #1 basically forces you into a specific "direction" of implementing From/Into, which means when you're dealing with conversion to/from foreign types the orphan rule can bite you.

    💬 0🔄 0⭐ 0
  • Wanjamuvlon@hachyderm.io
    Jul 28, 2026, 8:27 AM

    @laund @kroltan @aDot Huh, I always thought that From/Into being two separate traits (as opposed to just different functions in the same trait) was specifically to work around the orphan rule. That is, user code should generally impl From and use Into, which is slightly annoying to have to remember but also means we get to have both blanket (in std) and user-provided impls.

    But maybe I'm wrong?

    💬 0🔄 0⭐ 0