Skip to content

FnRefs are a problem #352

@danakj

Description

@danakj

I finally wrote a memory bug in subdoc and it was painful and i miss not having memory bugs.

The bug was using a fnref as an lvalue, which then is left with a dangling ref to a lambda. This is forbidden in the docs but I forgot. We need that clang-tidy to prevent it, or change FnRefs to heap alloc and be more like DynFnRef (like DynError) to do type-erasure to the heap.

Metadata

Metadata

Assignees

No one assigned

    Labels

    designDesign of the library systems as a whole, such as conceptssafetyMemory safety improvements

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions