Difference between std::function and a function pointer?

Function pointers only cover a narrow set of callable types; std::function can store lambdas with captures, bind results, and functors via type erasure.

Performance difference?

Indirect calls + type erasure make std::function heavier than a raw function pointer—often a few× in microbenchmarks.

When to use std::function?

When you need capturing lambdas or heterogeneous callables behind one interface.

When to use a function pointer?

Hot loops with C interop or a fixed callable signature without captures.

C++ std::function vs Function Pointers: Flexibility vs Speed

2026년 3월 28일 · 14분 읽기 · 수정 2026년 3월 28일 Intermediate comparison

이 글의 핵심

Compare std::function and function pointers: performance tradeoffs, capture support, and API design tips.

For encapsulating requests as callable objects (undo queues, jobs), the Command pattern builds on the same callback ideas.

Introduction: “How should I store callbacks?”

Function pointers are small and fast but cannot carry capturing lambdas. std::function is flexible but has overhead.

This article covers:

Capabilities
Benchmark trends
Design patterns

Comparison

Aspect	Function pointer	std::function
Capturing lambdas	No	Yes
Functors	No	Yes
Size / allocations	Pointer-sized	Larger; may heap for big captures
Speed	Faster indirect call	Slower

Performance (typical)

Microbenchmarks often show:

direct call fastest
function pointer next
std::function slowest (still fine for UI/event paths)

Prefer templates (template <class F>) for hot generic algorithms to avoid type erasure.

Guidelines

Situation	Prefer
C API / `extern "C"`	function pointer
Capturing lambda storage	`std::function` or template
Hot inner loop	pointer or templated callback

Pitfalls

Dangling captures in lambdas stored in std::function
std::bad_function_call if empty

Performance optimization

Keywords

std::function vs function pointer, type erasure, callback performance

Browse the C++ series
C++ Adapter Pattern