Skip to content

A join_view of safe_ranges should be able to model more than just input_range #641

@JohelEGP

Description

@JohelEGP

See ericniebler/range-v3#1401. I argue that join_view should additionally use safe_range so that it can model more than just input_range in more cases. This is for safe_ranges that aren't lvalue references, as that's already correct (see #598) and taken care of.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions