From: Peter C. <pca...@gm...> - 2022-05-11 07:55:49
|
Hi all When QuantLib is built with enabled QL_ENABLE_SESSIONS, users have to provide an implementation of sessionId(). Usually the sessions are used to enable thread-local singleton instances and consequently sessionId() will be implemented such that the current thread id is returned. More recent versions of QuantLib require C++11 as the minimum language standard and with that we are able to simplify the singleton implementation while always ensuring a thread-safe initialization of singleton instances. The proposed change is this https://github.com/lballabio/QuantLib/pull/1377 and comes with a removal of the sessionId() and a hard-wired assumption that there is a 1:1 relation between sessions and threads. The question for you is whether there are other uses of sessions out there which wouldn't be supported after the above change, i.e. where you use sessions differently from what I described above. Thanks Peter |