Skip to content

templates and iterators in stacktraces #808

@timotheecour

Description

@timotheecour

proposal

use a LRU cache with N (=10) most recent template/iterator calls, and upon stacktrace, show those to give more context

rationale

alternative would be to identify all exit points of templates/iterators, which may be doable but is harder to implement (and possibly inefficient)

links

see also nkComesFrom which IIRC had similar goals

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