TODOs in code

[whaleygeek]

FYI, here is a capture of the current list of TODO markers in the microbit-dal codebase:

MicroBitDevice.h

• TODO: Determine if any of this belongs in an mbed target definition.
• TODO: Review microbit-dal to place all such functions here.

MicroBitFiber.h

• TODO: Consider a split mode scheduler, that monitors used stack size, and maintains a dedicated, persistent

MicroBitHeapAllocator.h

• TODO: Consider caching recently freed blocks to improve allocation time.

MicroBitRadio.h

• TODO: The protocols implemented here do not currently perform any significant form of energy management,
• TODO: Meshing should also be considered - again a GLOSSY approach may be effective here, and highly complementary to
• TODO: This implementation only operates whilst the BLE stack is disabled. The nrf51822 provides a timeslot API to allow

MicroBitBLEManager.cpp // TODO: It would be much better to implement some sort of LRU/NFU policy here,

MicroBitDFUService.cpp // TODO: Raise a SYSTEM event here.

MicroBitHeapAllocator.cpp

• TODO: Consider caching recently freed blocks to improve allocation time.

DynamicPwm.cpp

• TODO: Merge into mbed, at a later date.

MicroBitDisplay.cpp

• TODO: Write a more efficient, complementary variation of this method for the case where //TODO: Put this in when we merge tight-validation

MicroBitRadio.cpp

• TODO: The protocols implemented here do not currently perform any significant form of energy management,
• TODO: Meshing should also be considered - again a GLOSSY approach may be effective here, and highly complementary to
• TODO: This implementation may only operated whilst the BLE stack is disabled. The nrf51822 provides a timeslot API to allow

MicroBitImage.cpp

• TODO: Consider an immutable flavour, which might save us RAM for animation spritesheets...

[finneyj]

Thanks @whaleygeek!

Some of these have been done already, so just need cleaning up in code. Others are more longer term concepts/optimizations that never quite got prioritized. great to bring these out here. I'll do a pass of these to separate these out.

Maybe we should turn some of these into "up for grabs" feature request issues...