Skip to content

to_prev iteration should be a thing #120

Description

@luketpeterson

We have to_next_step and to_next_val. We should have to_prev_step and to_prev_val.

They can be default implementations only, for now.

We ought to have benchmarks for them too.

I don't see a great need for to_prev_k_path + descend_last_k_path personally, so I'd rather not add them unless there is demand from a downstream project. I'm not against it, I just think it's probably superfluous.

Activity

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions