TheWisp/signals

Issues

• Not a bug, comment about the benchmark algorithm

  #25 opened 2 years ago by daneldanel
  2

• Trouble with nested connections

  #24 opened 3 years ago by stevenlovegrove
  0

• Severe potential bug

  #20 opened 4 years ago by Philippe91
  6

• Memory leak when the signal is destroyed before the fteng::connection is destroyed

  #23 opened 4 years ago by Philippe91
  1

• [question] Not thread safe?

  #19 opened 4 years ago by IceflowRE
  1

• Auto resolve ambiguously overloaded functions

  #1 opened 5 years ago by TheWisp
  1

• Missing features

  #6 opened 5 years ago by TheWisp
  2

• connect tries to copy move-only callbacks

  #18 opened 5 years ago by mikezackles
  2

• Can't compile functor lambdas in C++20

  #17 opened 5 years ago by Skomli
  1

• Suggestion: using std::unique_ptr instead of raw pointer

  #15 opened 5 years ago by hyperxor
  1

• Small object optimization for 1 or 2 slots

  #12 opened 5 years ago by TheWisp
  0

• Full benchmark on different specs / compilers / OS

  #11 opened 5 years ago by TheWisp
  0

• Unclear design when connecting a functor object with operator()

  #9 opened 5 years ago by TheWisp
  1

• Doesn't support custom allocators

  #10 opened 5 years ago by TheWisp
  0

• Don’t force saving the connection object

  #4 opened 5 years ago by TheWisp
  2

• Unclear design of connection type: copyable shared vs moveable unique

  #7 opened 5 years ago by TheWisp
  1

• Iteration with removal is slow

  #8 opened 5 years ago by TheWisp
  0

• Benchmark doesn’t represent typical behavior of virtual calls

  #5 opened 5 years ago by TheWisp
  1

• Moving signal can be slow

  #3 opened 5 years ago by TheWisp
  0

• Custom PMF solver / devirtualize target member function if virtual

  #2 opened 5 years ago by TheWisp
  0