Repository navigation

named_static_rtti; bad_call types without dynamic_type; std_rtti internal-linkage collisions - #127

Merged

jll63 merged 12 commits into

boostorg:developfrom

jll63:feature/dll

Oct 19, 2026

Merged

named_static_rtti; bad_call types without dynamic_type; std_rtti internal-linkage collisions#127
jll63 merged 12 commits into
boostorg:developfrom
jll63:feature/dll

Commits on Oct 18, 2026
- policies: named_static_rtti, a static_rtti that works across shared libraries
  
  jll63
  and
  claude
  committed
  be16c3f
- core: report bad_call argument types without dynamic_type
  
  jll63
  and
  claude
  committed
  d6a3630
- policies: std_rtti tells apart same-named classes with internal linkage
  
  jll63
  and
  claude
  committed
  4171d07
- review: fix the std_rtti scanner, class_of_vptr, and the type_index contract
  
  jll63
  and
  claude
  committed
  4af8967
- doc: rework shared_libraries.adoc for brevity
  
  jll63
  and
  claude
  committed
  d1adcd3
- simplify: named_static_rtti key, init_bad_call, tests
  
  jll63
  and
  claude
  committed
  66ce417
- policies: move named_static_rtti to its own header
  
  jll63
  and
  claude
  committed
  1cf3123
- test: keep inplace_vptr classes non-polymorphic in test_static_rtti_errors
  
  jll63
  and
  claude
  committed
  104316f
- doc: RttiFn::is_polymorphic has a policy-defined value
  
  jll63
  and
  claude
  committed
  fa6148b
- policies: is_polymorphic means the policy provides dynamic_type
  
  jll63
  and
  claude
  committed
  0e2c2ca
- core: bad_call reports the virtual arguments only
  
  jll63
  and
  claude
  committed
  2244812
- core: bad_call names the class a type-erased argument holds
  
  jll63
  and
  claude
  committed
  93bb513