ldionne/dyno

Issues

• Consider adding get and unsafe_get

  #19 opened 7 years ago by ldionne
  1

• Please submit to BOOST

  #48 opened 3 years ago by jwaterloo
  1

• Compile time code generation

  #60 opened 4 years ago by baryluk
  3

• Please add Conan Repository support

  #46 opened 7 years ago by jwaterloo
  9

• 'concept' and 'requires' are keywords in c++2a

  #56 opened 6 years ago by palebedev
  4

• Cannot find HanaConfig.cmake

  #39 opened 7 years ago by uknys
  4

• Unnecessary copies for non-macro remote_storage interfaces

  #52 opened 6 years ago by lucas93
  1

• Problem with GCC 8: Example does not compile b/c `poly::unerase_poly` is not declared.

  #55 opened 6 years ago by tinloaf
  3

• Wrong static_assert in detail::erase

  #54 opened 6 years ago by mikosz
  0

• Memory is not laundered after placement newing

  #53 opened 6 years ago by DarthRubik
  0

• make dyno::non_owning_storage the default

  #49 opened 7 years ago by jwaterloo
  1

• Please create a C++20 proposal

  #47 opened 7 years ago by jwaterloo
  1

• Documentation revisions: additional reasons for using this library

  #51 opened 7 years ago by jwaterloo
  0

• Arity and multiple SBO

  #50 opened 7 years ago by jwaterloo
  0

• Add test coverage for vtable policies

  #45 opened 7 years ago by ldionne
  0

• Add test coverage for storage policies

  #44 opened 7 years ago by ldionne
  0

• Refactor dyno::poly

  #43 opened 7 years ago by ldionne
  0

• Use a less generic user-defined literal

  #38 opened 7 years ago by samkellett
  4

• Allow specifying special member functions with DYNO_INTERFACE

  #40 opened 7 years ago by ArekPiekarz
  1

• poly is 24 bytes instead of 16 bytes

  #33 opened 7 years ago by ldionne
  3

• Tone down documentation about speed of vtable dispatch

  #37 opened 7 years ago by ldionne
  0

• Consider supporting method definitions in concepts

  #4 opened 7 years ago by ldionne
  3

• Dyno should build when optional dependencies are not found

  #31 opened 7 years ago by ldionne
  0

• The "stack storage" that often isn't.

  #32 opened 7 years ago by KubaO
  1

• Provide a vtable implementation based on a switch statement

  #36 opened 7 years ago by ldionne
  0

• Consider accepting custom allocators in `poly`

  #2 opened 8 years ago by ldionne
  0

• Consider supporting copy on write semantics

  #9 opened 8 years ago by ldionne
  0

• Add examples of passing custom concept maps to poly

  #25 opened 7 years ago by ldionne
  0

• Consider supporting arbitrary meta-data in vtables

  #26 opened 7 years ago by ldionne
  0

• Allow customizing policies independently

  #29 opened 7 years ago by ldionne
  0

• Consider adding support for assignment from another poly that has a subset of the requirements

  #24 opened 7 years ago by ldionne
  0

• DYNO_INTERFACE() customizable storage policy.

  #35 opened 7 years ago by lucas93
  1

• Very nice introduction!

  #27 opened 7 years ago by gabyx
  1

• "copy-construct" Function Not Found

  #28 opened 7 years ago by ricejasonf
  2

• Could we use a compressed vptr in some cases?

  #23 opened 7 years ago by ldionne
  0

• Allow querying whether a type models a concept

  #5 opened 7 years ago by ldionne
  2

• Document the requirements of Storage::get

  #21 opened 7 years ago by ldionne
  0

• Allow taking erased arguments by value

  #22 opened 7 years ago by ldionne
  0

• Consider adding assignment from anything

  #20 opened 7 years ago by ldionne
  0

• Add benchmarks against discriminated unions

  #16 opened 8 years ago by ldionne
  2

• Check signatures in concept maps

  #1 opened 8 years ago by ldionne
  1

• Allow te::poly to take a concept map at construction

  #7 opened 8 years ago by ldionne
  0

• Interface for using `te::concept_map` for static dispatch

  #8 opened 8 years ago by griwes
  6

• Invalid expression in default concept map

  #6 opened 8 years ago by ldionne
  0

• Consider support for concept hierarchies

  #3 opened 8 years ago by ldionne
  0