Hans Ekkehard Plesser

@JanVogelsang Thanks for checking and the new solutions! I slightly prefer the second option, but that is mainly based on the fact that I still haven't entirely wrapped my mind...

@JanVogelsang Under macOS 26, I could build your master out of the box with Apple Clang 17. The entire testsuite passes. I checked that `-lto=thin` was included in the compiler...

Another comment on this PR: I'd much prefer to get pynest-ng done first ...

> No idea how to interpret those Pytest aborts (see failing testsuite). Strange indeed. Does the testsuite pass locally on your computer? The worst problem seems to be the complete...

@med-ayssar Thanks for the PR! Have you confirmed that the problem still exists with NEST 3.9? It was originally reported against 3.4 and a number of things have happened in...

> Is it not better to use `decltype` to deduce the return type? > > `decltype(boost::get(s).get_node_id())` so basically you don't care about the precision type returned by the function, it...

@JanVogelsang Could you try what happens if, in the working variant, you create some node, e.g., a parrot neuron, before creating the music output proxy? I wonder if it might...

@med-ayssar Thanks for the analysis! I think for now, we should add clear documentation about the necessary order and then follow this up further. I should had not really thought...

I looked at it a little more. It seems to me that `music_cont_out_proxy` logically is very similar to `multimeter`. So we can change it to be used with normal `Connect(mcop,...

I will experiment a bit with a solution along the line sketched above.