Most developers will acknowledge how implementing crosscutting concerns such as logging, auditing, security and transactionality can adversely affect business logic implementation. Such concerns "seem" to increase the complexity of existing business logic, at times making it difficult if not impossible to clearly distinguish business logic from the crosscutting concern implementation.
How does Dart deal with this? If it doesn't currently have any mechanism to address this issue, are there plans to introduce a way to implement cross-cutting concerns?
Thanks.