Stavros Aronis

Duplicate indeed. Can be safely closed. (@benoitc's secondary comment is useful, so not doing it myself).

> Can you show the expected difference between the old output and the new one? I'm having a bit of a hard time just tracing in my mind what the...

Based on the sample code I am currently seeing on my Analytics account, there seems to no longer be any need for different javascript depending on the analytics version used,...

I will not work on this for the foreseeable future, but might get back to it at some later point.

More dimensions to explore when designing something like this: define **types** for such callbacks, and allow callback modules to annotate such functions accordingly. The behavior module could define precisely what...

I agree that this looks like a bug, and the proposed fix is exactly on the right track.

Hi @k32 ! This is a reasonable proposal, and one of my own "headaches" too: making it easier to "hide" "benign" racy operations from Concuerror, and still use them to...

This seems indeed to be a bug. I mistakenly thought that this was not a valid issue when I closed #102, but the justification given there is wrong. Thank you...

Hi @mikpe! Thank you for opening this issue! While I did try to make Concuerror "preserve" stacktraces for "user" code despite instrumentation, I did not test this feature thoroughly, so...

A similar issue has been in my TODO list for a while. :) https://github.com/aronisstav/Concuerror/issues/51 Let's talk requirements for a minimal working version: - add a `--output_type (pretty|raw)` flag (minor point:...