1) The design and implementation should not be too specific, which makes the solution too tricky to maintain.
Especially, even if we really really want to control the trigger policy, we should not do it in this very deep layer. It should be controlled in an outer scope.
2) The interface name exposes too much unnecessary internal implementation.
来源:
code review from https://gitee.com/openharmony/arkcompiler_ets_runtime/pulls/3317/
新值
描述:
1) The design and implementation should not be too specific, which makes the solution too tricky to maintain.
Especially, even if we really really want to control the trigger policy, we should not do it in this very deep layer. It should be controlled in an outer scope.
2) The interface name exposes too much unnecessary internal implementation information.
来源:
code review from https://gitee.com/openharmony/arkcompiler_ets_runtime/pulls/3317/
1) The design and implementation should not be too specific, which makes the solution too tricky to maintain.
Especially, even if we really really want to control the trigger policy, we should not do it in this very deep layer. It should be controlled in an outer scope.
2) The interface name exposes too much unnecessary internal implementation information.
来源:
code review from https://gitee.com/openharmony/arkcompiler_ets_runtime/pulls/3317/
新值
描述:
1) The design and implementation should not be too specific, which makes the solution too tricky to maintain.
Especially, even if we really really want to control the trigger policy, we should not do it in this very deep layer. It should be controlled in an outer scope.
2) The interface name exposes too much unnecessary internal implementation information.
来源:
code review from https://gitee.com/openharmony/arkcompiler_ets_runtime/pulls/3317