Skip to content

Should the range_* functions be in the prelude as well? #9242

Closed

Description

@dcrewi

Shouldn't range_inclusive, range_step, and range_step_inclusive be included in the prelude?

Activity

  1. thestinger commented on Sep 17, 2013

    @thestinger
    Contributor

    There's also count for an infinite stream. There has to be a limit on what we're going to put in the prelude, but I don't know where the line should be drawn.

  2. alexcrichton commented on Sep 17, 2013

    @alexcrichton
    Member

    I don't think we want to add too many things to the prelude. I think that because range is kinda the way to iterate over integers, it's well placed in the prelude, but these aren't necessarily as common as the range pattern in general.

  3. added a commit that references this issue on Jul 28, 2022
    af33de7
  4. added a commit that references this issue on Aug 21, 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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions