Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The `eval-cond` signal is less powerfull that its the same named `eval-cond` observation (as it is not fired from the Lisp code), so we should either deprecate it or even remove it (to prevent confusion between singal and observation that have same meaning but different semantics). With that said, the semantics of `eval-cond` is the same as it was befor 2.1.0 (i.e., starting from 1.5 to 2.0 inclusive), it has changed only in 2.1.0 and now we are rolling back it again. The future of this signal is unclear. Possible we will be able to enable it in the 2.1.0 semantics by enabling two modes of execution of the Primus code - analysis and modelling, but this requires a lot of effort and many not work at the end, so it might be that we will remove this signal at all from Primus Lisp interface in 2.2.0.
- Loading branch information