This is technically an ABI break of mircommon because we expose MirEvent .. Though our users are not constructing Events on the stack ~ we kind of allow it and do it ourselves in one place in mirserver.
The whole cleanup work will involve an ABI break anyhow..
This is technically an ABI break of mircommon because we expose MirEvent .. Though our users are not constructing Events on the stack ~ we kind of allow it and do it ourselves in one place in mirserver.
The whole cleanup work will involve an ABI break anyhow..