Open liziyi75 opened 4 days ago
Yeah, there is a plan; currently there is one more design issue to be solved, mainly how to handle different return states in a more explicit way to avoid not being able to see potential transitions on the transition table, it's not a big issue and solution already exist, is just not ideal yet, so need some more thinking through but the plan is to add all UML-2.5 features eventually.
That's cool, thanks!
It seems that version 3 is more aligned with C++ itself, making it easier to express requirements and improving performance. Will there be support for features like orthogonal regions, on_entry/on_exit, etc.? I am very much looking forward to the release of version 3. Thank you!