Skip to content

Implement overloaded slice notation #17177

Closed

Description

@alexcrichton

Tracking issue for rust-lang/rfcs#198

Activity

  1. alexcrichton commented on Sep 11, 2014

    @alexcrichton
    MemberAuthor

    Nominating, I believe this is a very important syntax to have.

  2. alexcrichton commented on Sep 11, 2014

    @alexcrichton
    MemberAuthor

    cc #17177, this may just be a dupe of that.

  3. aturon commented on Sep 11, 2014

    @aturon
    Contributor

    @alexcrichton This is #17177 :-)

    Note that if we end up making Vec<T> deref to [T], the need for the [] notation becomes less pressing.

  4. alexcrichton commented on Sep 11, 2014

    @alexcrichton
    MemberAuthor

    oops: cc #14983

  5. pnkfelix commented on Sep 11, 2014

    @pnkfelix
    Contributor

    We can add this syntax backwards-compatibly.

    Assigning P-low, not 1.0 blocker.

  6. nrc commented on Sep 15, 2014

    @nrc
    Member

    I am implementing

  7. aturon commented on Sep 15, 2014

    @aturon
    Contributor

    @nick29581 Awesome!

  8. nrc commented on Sep 16, 2014

    @nrc
    Member

    See #17293 and #17273 for some work left to do.

  9. nrc commented on Sep 16, 2014

    @nrc
    Member

    and #17295

  10. nodakai commented on Dec 19, 2014

    @nodakai
    Contributor

    @nick29581 You listed three issues #17293 #17273 and #17295 but only the first among them is still open. Is that the reason why we still need feature(slicing_syntax) for this syntax?

  11. nrc commented on Dec 19, 2014

    @nrc
    Member

    @nodakai in general, feature gates are required until we are absolutely sure that a feature should be in Rust and stay in its current form. We are not there yet with slicing notation. In fact, we are tweaking the implementation and the surface syntax at the moment (see #19795).

  12. nodakai commented on Dec 21, 2014

    @nodakai
    Contributor

    @nick29581 I see, so the slicing notation is tracked by 0439-cmp-ops-reform rather than 0198-slice-notation now.

  13. nrc commented on Dec 22, 2014

    @nrc
    Member

    @nodakai I wouldn't say either RFC tracks slicing notation - both contain aspects of the design

  14. added a commit that references this issue on May 19, 2024
  15. added a commit that references this issue on Jul 5, 2026
  16. added a commit that references this issue on Jul 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    B-RFC-approvedBlocker: Approved by a merged RFC but not yet implemented.P-lowLow priority

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions