You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 7, 2020. It is now read-only.
The current BWL interface has evolved historically into its current shape. Because of that, it is a bit more complicated than strictly necessary for prplMesh purposes. In addition, there are probably a few functions that are not really needed.
Several new bwl backends will be added for different chipsets. Therefore, the BWL interface will become external API that is going to be more difficult to change. Thus, we should freeze that API. It is therefore important to do any refactoring now, before more backends are added.
Look at BWL as a whole and determine which API is really needed, and refactor it in that direction.
Description
The current BWL interface has evolved historically into its current shape. Because of that, it is a bit more complicated than strictly necessary for prplMesh purposes. In addition, there are probably a few functions that are not really needed.
Several new bwl backends will be added for different chipsets. Therefore, the BWL interface will become external API that is going to be more difficult to change. Thus, we should freeze that API. It is therefore important to do any refactoring now, before more backends are added.
Look at BWL as a whole and determine which API is really needed, and refactor it in that direction.
This ties in with #448 and #435.
The text was updated successfully, but these errors were encountered: