There may be a misunderstanding as to the role of SG14, and WG21: we
are not a mechanism for distributing libraries, we are trying to
improve/extend the specification of the C++ language (and in the case
of SG14, with a focus on embedded, financial, and gamedev). So what
we'd want to see is a description of what the proposed thing is
supposed to do. An implementation may be useful to exercise the
proposal, but it is not the focus of this group. As you've
mentioned, there has been previous standardization work in this area:
it would probably be good to discuss why that previous work is
insufficient, and how yours extends it.

Also: please disclose the role/use of AI in this project.

On Sat, Aug 15, 2026 at 5:32 AM ycjin_kim via SG14
<sg14_at_[hidden]> wrote:
>
> Hi SG14,
>
> My name is Kim, a developer interested in embedded systems. I'd like to share a project I've been working on called "Embedded Function" and get the group's feedback.
>
> **Project Introduction**
> `Embedded Function` is a lightweight, header-only library that provides a collection of heap-free polymorphic function wrappers (like `ebd::fn`, `ebd::unique_fn`, `ebd::fn_ref`). It's designed for resource-constrained or high-performance environments like game development and embedded systems. The library is freestanding, supports C++11 through C++26, and offers several performance optimizations like branch elimination and zero-stack overhead. It contains only one header file, so it is Godbolt friendly.
>
> **Why I'm sharing this with SG14**
> I understand that SG14 has been interested in a non-allocating `inplace_function` for a long time. While the `stdext::inplace_function` implementation exists in the SG14 repository, it seems the standardization effort has not progressed recently. My library aims to be a modern, production-ready alternative. It offers several variants (`fn`, `unique_fn`, `classic_fn`, `fn_ref`) to cover different use cases, similar to what `std::function`, `std::copyable_function`, and `std::function_ref` provide.
>
> I believe `Embedded Function` could serve as a valuable data point or even a potential reference implementation for any future standardization efforts in this area.
>
> **Questions for the group**
> - Does the direction of `Embedded Function` align with what SG14 envisions for a standard `inplace_function`?
> - Are there any features or design choices you think are missing or could be improved?
> - What would be the best way to contribute this work to the ongoing discussion?
>
> The project is open-source on GitHub: https://github.com/Kim-J-Smith/Embedded-Function. I'd be very grateful for any feedback, suggestions, or criticism.
>
> Best regards,
> Kim J. Smith
>
> _______________________________________________
> SG14 mailing list
> SG14_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg14