As we revisit the C++ implementation of GR 4.0, this doc seeks to define the intended usage of GNU Radio and where we can modify the behavior to which users are accustomed.
NOTE: This is not intended to just represent the API as it currently stands, but elicit discussion re: how far we are willing to stray from the current GNU Radio usage paradigm. Examples are not dictating API, but provided to show generally how objects interact
- Keep Python interface a thin wrapper over C++ API
- Avoid Python-only implementations outside of OOT modules
- Modular runtime swappable components both in and out of tree
- Get block developers to "insert code here" without lots of boilerplate or complicated code