Class duds::data::Unit: Some units, like Watts cubed, cannot be represented. Consider larger fields. Maybe use larger fields on another type used for intermediate results and unusual units and allow implicit conversions.
Member duds::general::DataSize< Bits >::DataSize (const DataSize< ConvBits > &ds): The constructor should fail to compile when not used in an explicitly constexpr expression if Bits divided by ConvBits has a reminder, and the parameter ds is constexpr.
Member duds::general::StackTrace: The captured stack trace shows where this object is created rather than where the exception is thrown. The function throwing the exception may not be in the trace. However, the location of the throw is included in other exception information by DUDS_THROW_EXCEPTION and BOOST_THROW_EXCEPTION.
Class duds::hardware::devices::clocks::GenericLinuxClock< SVT, SQT, TVT, TQT >: Jitter and stability are ignored and not reported.
Member duds::hardware::devices::displays::HD44780::off (): Name isn't technically correct; change it.
Member duds::hardware::devices::displays::HD44780::on (): Name isn't technically correct; change it.
Member duds::hardware::devices::displays::ST7920::off (): Name isn't technically correct; change it.
Member duds::hardware::devices::displays::ST7920::on (): Name isn't technically correct; change it.
Class duds::hardware::devices::instruments::AM2320: The CRC value is not checked because the calculated value never matches what the device sends. Even using the code from the datasheet produces the same non-matching result computed here.
Member duds::hardware::devices::instruments::AM2320::sample (): The CRC value is not checked because the calculated value never matches what the device sends. Even using the code from the datasheet produces the same non-matching result computed here.
Member duds::hardware::devices::instruments::TSL2591::brightness () const: The value is wrong. I'm not sure which numbers on the datasheet to use to generate the number, or even if any of them are the ones needed. Changing the gain will result in very different results for the same light.
Member duds::hardware::devices::instruments::TSL2591::brightnessIr () const: The value is wrong. I'm not sure which numbers on the datasheet to use to generate the number, or even if any of them are the ones needed. Changing the gain will result in very different results for the same light.
Member duds::hardware::devices::instruments::TSL2591::scale: The value is almost certainly wrong.
Member duds::hardware::interface::DigitalPinSetAccess::modifyConfig (const DigitalPinConfig &conf) const: The set may not have a gap (pin ID -1). This will result in a DigitalPinConfigError exception being thrown.
Member duds::hardware::interface::DigitalPinSetAccess::output (bool state) const: The set may not have a gap (pin ID -1). This will result in a DigitalPinConfigError exception being thrown.
Member duds::hardware::interface::DigitalPinSetAccess::write (Int val, int bits) const: Will fail for unsigned types with negative values.
Member duds::hardware::interface::linux::SysFsPort::configurePort (unsigned int localPinId, const DigitalPinConfig &cfg, DigitalPinAccessBase::PortData *): Is this the right place for such a check? Should it be done by the caller?
Member duds::hardware::interface::MasterSyncSerial::condStart (): Exception changed to SyncSerialNotOpen
Member duds::hardware::interface::MasterSyncSerial::condStop (): Exception changed to SyncSerialNotOpen
Namespace duds::time::interstellar: Fix named types!
Member duds::time::planetary::LeapSeconds::readZoneinfo (const std::string &zoneinfo): The current until time (currUntil) is not changed. Is an acceptable time available?
Member duds::ui::graphics::BppFont::render (const std::u32string &text, Flags flags=AlignLeft): Only tested for rendering a single line of text.
Member duds::ui::graphics::BppFont::render (const std::string &text, Flags flags=AlignLeft): Only tested for rendering a single line of text.
Member duds::ui::menu::MenuView::insertion (std::size_t idx): Can run simultaneously with jump(), but cannot lock block because that would cause a deadlock with update() if a menu item responded to MenuItem::chose() by inserting or removing an item.
Member duds::ui::menu::MenuView::removal (std::size_t idx): Can run simultaneously with jump(), but cannot lock block because that would cause a deadlock with update() if a menu item responded to MenuItem::chose() by inserting or removing an item.
Member duds::ui::menu::renderers::BppMenuRenderer::addScrollBar (std::uint16_t width=1, std::uint16_t margin=1, std::uint16_t minsize=4, ScrollBarPlacement place=ScrollRight): The scroll bar will be sized as though menu items that are hidden from view are present on the display.
Member DUDS_THROW_EXCEPTION (x): Boost 1.65.0, and possibily earler versions, include push_options.pp and pop_options.pp, which are not part of the Boost install. The issue was resolved in Boost 1.65.1.