Skip to content

templates and iterators in stacktraces #797

@timotheecour

Description

@timotheecour

proposal

if problem is hard or expensive, 1 practical approach would be a MRU cyclic buffer of template/iterators most recently calls so that at least we know what was called recently

unless there's an easy way to find all the exits of a template/iterator

links

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